From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org, akpm@zip.com.au, raul@pleyades.net
Subject: Re: Mount corrupts an ext2 filesystem on a RAM disk
Date: Tue, 16 Jul 2002 00:29:28 -0400 [thread overview]
Message-ID: <a05111609b958efe305c4@[129.98.90.227]> (raw)
In-Reply-To: <Pine.LNX.3.95.1020715143606.232A-100000@chaos.analogic.com>
>It also works okay here. Maybe, just maybe, you booted with initrd,
>but did't unmount it before you started mucking with it `umount /initrd`
>in the script below.
>
I retested the ramdisk without executing the initial umount
instructions you proposed and saw the problem as I expected, but when
I first ran your umount instructions and then tested again, the fsck
problem didn't show up!
I tested this on all three of my boxes and they all behave the same.
So I guess this means there is a problem somewhere else, but I don't know what:
1) initrd really had still been mounted though df does not detect it.
2) there is no ghost initrd mounted, but merely executing bogus
umount instructions in some unknown way prevents the problem.
If it is the first one, there are two questions: why is initrd not
getting unmounted and why doesn't it show up in df?
If it is the second one, then what could be going on?
--
Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
next prev parent reply other threads:[~2002-07-16 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 16:46 Maurice Volaski
2002-07-15 18:39 ` DervishD
2002-07-15 18:40 ` Richard B. Johnson
2002-07-16 4:29 ` Maurice Volaski [this message]
2002-07-16 16:43 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2002-04-03 16:52 Maurice Volaski
2002-04-03 19:16 ` Andrew Morton
2002-04-03 20:41 ` Maurice Volaski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a05111609b958efe305c4@[129.98.90.227]' \
--to=mvolaski@aecom.yu.edu \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@pleyades.net \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®