mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Kris Urquhart <kurquhart@littlefeet-inc.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: ext2/mount - multiple mounts corrupts inodes
Date: Wed, 30 Jan 2002 16:37:30 -0700	[thread overview]
Message-ID: <20020130163730.N763@lynx.adilger.int> (raw)
In-Reply-To: <B9F49C7F90DF6C4B82991BFA8E9D547B1256F4@BUFORD.littlefeet-inc.com>
In-Reply-To: <B9F49C7F90DF6C4B82991BFA8E9D547B1256F4@BUFORD.littlefeet-inc.com>; from kurquhart@littlefeet-inc.com on Wed, Jan 30, 2002 at 03:07:19PM -0800

On Jan 30, 2002  15:07 -0800, Kris Urquhart wrote:
> [1.] One line summary of the problem: 
> A mount of an already mounted ext2 partition corrupts inodes if there have
> been recent writes without an intervening sync.

This _should_ be handled OK by the kernel simply by not mounting the
filesystem the second time.  If you try and mount it a second time it
_should_ just do a "bind" mount instead of a real mount, I think.

<stating the obvious>
Rather than mounting the device to try and see if it is already
mounted, use /proc/mounts or /etc/mtab or "df" or "mount" output
instead.  Doctor, it hurts when I do this... ;-).
</stating the obvious>

Granted, this does appear to be a bug so the above will only work
around it and not fix it.  Al Viro is the one to pester about it.
Hopefully he will see this email and reply (== fix the problem).

> [4.] Kernel version (from /proc/version): 
> Linux version 2.4.10 (kurquhart@bay.sw.littlefeet-inc.com) (gcc version
> egcs-2.91.66 
> 19990314/Linux (egcs-1.1.2 release)) #1 Wed Jan 30 09:46:52 PST 2002

The 2.4.10 kernel is a bad one to use for several reasons, don't use it.

Cheers, Andreas

PS - nice bug report, if only all of them were this useful.
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2002-01-30 23:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 23:07 Kris Urquhart
2002-01-30 23:37 ` Andreas Dilger [this message]
2002-01-31  0:14   ` Alexander Viro
2002-01-31  6:35   ` H. Peter Anvin
2002-01-31  1:27 Kris Urquhart
2002-01-31  4:45 ` Andreas Dilger
2002-01-31  5:05 ` Alexander Viro
2002-01-31 17:28 Kris Urquhart
2002-01-31 21:57 ` Alexander Viro
2002-01-31 17:31 Kris Urquhart
2002-01-31 23:46 Kris Urquhart
2002-02-01  1:00 Ishan O. Jayawardena

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=20020130163730.N763@lynx.adilger.int \
    --to=adilger@turbolabs.com \
    --cc=kurquhart@littlefeet-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®