From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: jack@suse.cz, linux-ext4@vger.kernel.org
Subject: Re: ext2 issues with xfstests 113
Date: Mon, 31 May 2010 19:57:47 +0200 [thread overview]
Message-ID: <20100531175747.GD5334@quack.suse.cz> (raw)
In-Reply-To: <20100531094625.GA10283@lst.de>
On Mon 31-05-10 11:46:25, Christoph Hellwig wrote:
> fsck from util-linux-ng 2.17
> e2fsck 1.41.11 (14-Mar-2010)
> Pass 1: Checking inodes, blocks, and sizes
> Inode 22, i_blocks is 20512, should be 16512. Fix? no
>
> Inode 31, i_blocks is 20512, should be 16512. Fix? no
>
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Block bitmap differences: -(8090--8191) -(43829--44328) -(51784--52181)
> Fix? no
Are you able to reproduce this? Because for me ext2 runs went just
fine...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-05-31 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 9:46 ext2 issues with xfstests 113 Christoph Hellwig
2010-05-31 17:57 ` Jan Kara [this message]
2010-05-31 18:01 ` Christoph Hellwig
2010-05-31 21:31 ` Jan Kara
[not found] ` <20100601090337.GA28085@lst.de>
2010-06-01 10:26 ` Jan Kara
2010-06-01 13:08 ` Jan Kara
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=20100531175747.GD5334@quack.suse.cz \
--to=jack@suse.cz \
--cc=hch@lst.de \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).