From: Andreas Dilger <adilger-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org>
To: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
Cc: linux-ext4 <linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Lustre-discuss
<Lustre-discuss-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org>
Subject: Re: [PATCH] Correction to check_filetype()
Date: Sat, 31 Mar 2007 02:16:24 -0600 [thread overview]
Message-ID: <20070331081624.GF5967@schatzie.adilger.int> (raw)
In-Reply-To: <20070331004417.GJ3198-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
On Mar 30, 2007 20:44 -0400, Theodore Tso wrote:
> On Wed, Feb 21, 2007 at 02:45:59PM +0530, Kalpak Shah wrote:
> > If the mode of a directory gets corrupted, check_filetype() makes
> > wrong decisions for all its sub-directories. For example, using
> > debugfs we can corrupt the mode of a directory to 0140755 (i.e. a
> > socket). e2fsck will set the filetype of all its subdirectories as 6
> > (filetype for socket). All the subdirectories would be moved to
> > lost+found, and in second run of e2fsck their filetype would be set
> > back to 2.
>
> Um, I'm not seeing this. Using stock e2fsprogs, given the following
> test image, I'm not seeing the behavior you describe.
The log of the e2fsck (on a test filesystem with deliberately introduced
corruption) is available at:
https://bugzilla.lustre.org/show_bug.cgi?id=11645
I've also added a testcase (created by making a parent directory with several
subdirs, then using debugfs to change the mode of the parent directory).
https://bugzilla.lustre.org/attachment.cgi?id=9958
(also attached here).
It doesn't exhibit the filetype breakage in the upstream e2fsck because the
test is run with the patch applied, but it does still show the "size is wrong
on second e2fsck" problem you observed. The test case is created as if that
problem was also fixed already (i.e. second e2fsck is clean).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
[-- Attachment #2: e2fsprogs-tests-f_check_filetype.patch --]
[-- Type: application/octet-stream, Size: 14690 bytes --]
[-- Attachment #3: Type: text/plain, Size: 190 bytes --]
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
next prev parent reply other threads:[~2007-03-31 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 9:15 [PATCH] Correction to check_filetype() Kalpak Shah
2007-02-21 11:49 ` Kalpak Shah
2007-02-21 14:49 ` Peter Staubach
[not found] ` <45DC5BFF.4000302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-02-21 15:26 ` Kalpak Shah
2007-03-31 0:44 ` Theodore Tso
[not found] ` <20070331004417.GJ3198-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-03-31 8:16 ` Andreas Dilger [this message]
2007-03-31 12:35 ` Theodore Tso
2007-03-31 14:39 ` Theodore Tso
2007-03-31 19:40 ` Kalpak Shah
[not found] ` <20070331143926.GG25539-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-04-03 17:37 ` Andreas Dilger
2007-04-03 19:58 ` Theodore Tso
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=20070331081624.GF5967@schatzie.adilger.int \
--to=adilger-kypl3ael/zsakbo8gow8eq@public.gmane.org \
--cc=Lustre-discuss-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).