From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error whilst running "tune2fs -j"
Date: Fri, 04 Apr 2003 17:59:13 -0800 [thread overview]
Message-ID: <5750000.1049507953@flay> (raw)
In-Reply-To: <20030404155633.29ed6f8a.akpm@digeo.com>
>> Anyone see this before? This was 2.5.65-mjb2 running on my laptop,
>> at the start of a "tune2fs -j" ....
>>
>> buffer layer error at fs/buffer.c:395
>
> grrr. This means that the block_dev layer somehow managed to get the
> filesystem softblocksize confused. There is something lurking in there. As
> usual, if I could reproduce it I could fix it.
>
> Was the fs mounted at the time?
Yes, was my root fs.
> What version of e2fsprogs?
Standard debian woody:
mbligh@flay:~/tmp$ apt-cache show e2fsprogs
Package: e2fsprogs
Essential: yes
Priority: required
Section: base
Installed-Size: 832
Maintainer: Yann Dirson <dirson@debian.org>
Architecture: i386
Version: 1.27-2
Provides: libcomerr2, libss2, libext2fs2, libe2p2, libuuid1
Pre-Depends: libc6 (>= 2.2.4-4)
Suggests: gpart, parted, e2fsck-static
Conflicts: e2fslibsg, dump (<< 0.4b4-4), quota (<< 1.55-8.1)
Filename: pool/main/e/e2fsprogs/e2fsprogs_1.27-2_i386.deb
Size: 335402
> Can you reproduce it?
Not easily, I fear ... since it's a pain in the butt to remove an ext3
journal on the root fs once mounted. I suppose I could boot from CD
or something ... will try to recreate on a less valuable box over
the weekend ;-)
I had been having some other trouble with the fs (power cycled a couple
of times for silly reasons), but it had just ext2 fscked. I suppose there
*might* have been some corruption, but seems unlikely.
M.
next prev parent reply other threads:[~2003-04-05 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 23:25 Error whilst running "tune2fs -j" Martin J. Bligh
2003-04-04 23:56 ` Andrew Morton
2003-04-05 1:59 ` Martin J. Bligh [this message]
2003-04-05 2:25 ` Andrew Morton
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=5750000.1049507953@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.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