From: Andreas Dilger <adilger@turbolabs.com>
To: Kris Urquhart <kurquhart@littlefeet-inc.com>
Cc: "'Alexander Viro'" <viro@math.psu.edu>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: ext2/mount - multiple mounts corrupts inodes
Date: Wed, 30 Jan 2002 21:45:52 -0700 [thread overview]
Message-ID: <20020130214552.Q763@lynx.adilger.int> (raw)
In-Reply-To: <B9F49C7F90DF6C4B82991BFA8E9D547B1256F7@BUFORD.littlefeet-inc.com>
In-Reply-To: <B9F49C7F90DF6C4B82991BFA8E9D547B1256F7@BUFORD.littlefeet-inc.com>; from kurquhart@littlefeet-inc.com on Wed, Jan 30, 2002 at 05:27:42PM -0800
On Jan 30, 2002 17:27 -0800, Kris Urquhart wrote:
> When using a disk partition, however, the second mount
> appears to fail, but then yields the exact same results
> as the loop device example. It appears that the second
> mount actually replaced the first one, without giving the
> first one a chance to sync to disk?
It shouldn't have done so.
> + find /mnt/hd -ls
> 2 1 drwxr-xr-x 3 root root 1024 Dec 31 15:17 /mnt/hd
> 11 12 drwxr-xr-x 2 root root 12288 Dec 31 15:17
> /mnt/hd/lost+found
> find: /mnt/hd/tar: Input/output error
> find: /mnt/hd/zcat: Input/output error
Any interesting output in 'dmesg' when this happens?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-31 4:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 1:27 Kris Urquhart
2002-01-31 4:45 ` Andreas Dilger [this message]
2002-01-31 5:05 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2002-02-01 1:00 Ishan O. Jayawardena
2002-01-31 23:46 Kris Urquhart
2002-01-31 17:31 Kris Urquhart
2002-01-31 17:28 Kris Urquhart
2002-01-31 21:57 ` Alexander Viro
2002-01-30 23:07 Kris Urquhart
2002-01-30 23:37 ` Andreas Dilger
2002-01-31 0:14 ` Alexander Viro
2002-01-31 6:35 ` H. Peter Anvin
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=20020130214552.Q763@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=kurquhart@littlefeet-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®