From: Andreas Dilger <adilger@clusterfs.com>
To: Wayne Whitney <whitney@math.berkeley.edu>
Cc: LKML <linux-kernel@vger.kernel.org>, ext2-devel@lists.sourceforge.net
Subject: Re: [OOPS 2.5.5-dj2] ext3 BUG in do_get_write_access()
Date: Fri, 1 Mar 2002 11:59:32 -0700 [thread overview]
Message-ID: <20020301115932.T22608@lynx.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.44.0202281703130.4893-100000@mf1.private>
In-Reply-To: <Pine.LNX.4.44.0202281703130.4893-100000@mf1.private>; from whitney@math.berkeley.edu on Thu, Feb 28, 2002 at 05:19:44PM -0800
On Feb 28, 2002 17:19 -0800, Wayne Whitney wrote:
> I managed to generate the oops below on 2.5.5-dj2 by doing the following:
> cp -ax / /mnt &
> <some delay, don't know if it matters>
> tune2fs -L root /dev/hdc5
>
> tune2fs -L should be safe on a mounted filesystem, non?
Maybe. It used to be that the superblock was not journaled, but I think
that recently changed. This means that if tune2fs modified the superblock
and then a transaction also tried to modify it, the superblock would be
dirty and not part of a transaction, so an assertion would trigger.
It may be that we need to add journaled ioctls to ext3 to change the data
fields in the superblock, or find some other way to do this safely (maybe
Jeff Garzik's ext3meta filesystem to just read/write the "label" file?).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-03-01 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 1:19 Wayne Whitney
2002-03-01 18:59 ` Andreas Dilger [this message]
2002-03-01 19:41 ` Stephen C. Tweedie
2002-03-01 20:15 ` Chris Mason
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=20020301115932.T22608@lynx.adilger.int \
--to=adilger@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@math.berkeley.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®