From: Jeff Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Alexander Zarochentsev <zam@namesys.com>,
reiserfs-list@namesys.com, Graham Leggett <minfrin@sharp.fm>
Subject: Re: Undeletable files...
Date: Tue, 18 Apr 2006 09:53:06 -0400 [thread overview]
Message-ID: <4444EF42.7030507@suse.com> (raw)
In-Reply-To: <44452C44.9040000@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> Was this a 3.5/3.6 conversion bug? I thought we figured it out
> once.... I just can't remember the figuring....
Oh ok, I see where you're going with it. There was the bug where the
inode attribute bit in the super would claim that inode attribute were
valid and then cause problems when they were enabled by default. That
patch wasn't in mainline until 2.6.12.
The kernel in the bug report is 2.6.9 w/ RH patches. I haven't read the
source, but I doubt they would have backported that bug.
At any rate, Graham, can you post your dmesg and the output of "grep
kernel: /var/log/messages"? If you're seeing unexplained permissions
errors, I'd like to see the logs as the most likely source is corruption.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFERO9CLPWxlyuTD7IRAk+4AJ99lehSoURYKL9+DeBcLlaWA3rHAgCfdyo/
DRHDvbfPE7b32m/i8pveoRo=
=/RXV
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-04-18 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:14 Undeletable files Graham Leggett
2006-04-15 19:58 ` Alexander Zarochentsev
[not found] ` <444353D7.5000302@namesys.com>
2006-04-16 21:10 ` Jeffrey Mahoney
[not found] ` <44445AED.6080905@namesys.com>
2006-04-17 15:26 ` Jeff Mahoney
[not found] ` <44450FCE.4060608@namesys.com>
2006-04-18 4:58 ` Jeff Mahoney
[not found] ` <44452C44.9040000@namesys.com>
2006-04-18 13:53 ` Jeff Mahoney [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=4444EF42.7030507@suse.com \
--to=jeffm@suse.com \
--cc=minfrin@sharp.fm \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.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 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.