From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
aneesh.kumar@linux.vnet.ibm.com,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUG] 2.6.27-rc1 - Filesystem warning on ext4 with e2fsck
Date: Mon, 11 Aug 2008 21:19:29 +0530 [thread overview]
Message-ID: <48A05F89.4070702@linux.vnet.ibm.com> (raw)
In-Reply-To: <48A04C40.1040206@redhat.com>
Eric Sandeen wrote:
> Kamalesh Babulal wrote:
>> Hi,
>>
>> After running the fsx linux test on the ext4 partition mounted with
>> -o errors=panic,journal_async_commit, filesystem check is reporting
>> warning
>>
>> # /usr/local/e2fsprogs/sbin/e2fsck -fnv /dev/sda6
>> e2fsck 1.41.0 (10-Jul-2008)
>> Pass 1: Checking inodes, blocks, and sizes
>> Pass 2: Checking directory structure
>> Pass 3: Checking directory connectivity
>> /lost+found not found. Create? no
>>
>> Pass 4: Checking reference counts
>> Pass 5: Checking group summary information
>>
>> /dev/sda6: ********** WARNING: Filesystem still has errors **********
>
> Was lost+found manually removed between mkfs & fsck? (did you do an rm
> -rf * or similar ?) That'd produce exactly the above warning, since you
> told e2fsck "-n" ...
>
> -Eric
> --
Hi Eric,
Yes, the test program does a rm -rf * of the partition and
usr/local/e2fsprogs/sbin/e2fsck -fvp /dev/sda6 helps. Sorry
for the noise.
--
Thanks & Regards,
Kamalesh Babulal.
prev parent reply other threads:[~2008-08-11 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 10:20 [BUG] 2.6.27-rc1 - Filesystem warning on ext4 with e2fsck Kamalesh Babulal
[not found] ` <48A0127E.6000505-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-08-11 14:27 ` Eric Sandeen
2008-08-11 15:49 ` Kamalesh Babulal [this message]
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=48A05F89.4070702@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=apw@shadowen.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).