From: Oleg Drokin <green@linuxhacker.ru>
To: sgtphou@fire-eyes.dynup.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0: reiserfs errors: reiserfs_read_locked_inode and friends
Date: Fri, 19 Dec 2003 14:49:14 +0200 [thread overview]
Message-ID: <200312191249.hBJCnEFp022715@car.linuxhacker.ru> (raw)
In-Reply-To: 3FE28116.3000406@fire-eyes.dynup.net
Hello!
fire-eyes <sgtphou@fire-eyes.dynup.net> wrote:
fe> I have been experimenting between 2.4.23 and 2.6.0-test{5,6,7,8,9,10,11}
fe> and now 2.6.0.
fe> Starting with -test11, I noticed often that I could not perform a
fe> startx, and as root got permission denied trying to execute or even list
fe> some files. I also notice this in 2.6.0. Dropping back to 2.4.23, I can
fe> perform the mentioned actions.
fe> Dec 18 22:29:40 localhost kernel: hda: set_drive_speed_status:
fe> status=0x58 { DriveReady SeekComplete DataRequest }
fe> Dec 18 22:29:40 localhost kernel: ide0: Drive 0 didn't accept speed
fe> setting. Oh, well.
fe> Dec 18 22:29:40 localhost kernel: blk: queue dfd8f800, I/O limit 4095Mb
fe> (mask 0xffffffff)
fe> Dec 18 22:29:40 localhost kernel: is_tree_node: node level 0 does not
fe> match to the expected one 2
Sounds that somehow some blocks read by reiserfs are zero-filled.
fe> Here is what i'm passing to 2.6.0 via grub:
fe> root=/dev/hda6 ide0=autotune ide1=autotune
What if won't pass "ide0=autotune ide1=autotune" part for 2.6? Does
anything changes?
Bye,
Oleg
prev parent reply other threads:[~2003-12-19 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 4:39 2.6.0: reiserfs errors: reiserfs_read_locked_inode and friends fire-eyes
2003-12-19 12:49 ` Oleg Drokin [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=200312191249.hBJCnEFp022715@car.linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sgtphou@fire-eyes.dynup.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.