public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe <rouquier.p@wanadoo.fr>
To: Ragnar Hojland Espinosa <ragnar@linalco.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs 3.6 problem with test9
Date: Tue, 11 Nov 2003 18:33:56 +0100	[thread overview]
Message-ID: <1068572036.344.8.camel@Genesyme> (raw)
In-Reply-To: <20031111135948.GA5229@linalco.com>

Le mar 11/11/2003 à 14:59, Ragnar Hojland Espinosa a écrit :
> On Tue, Nov 11, 2003 at 01:19:57PM +0100, Philippe wrote:
> > Hello,
> > recently I noticed some annoying problems whenever I try to access some
> > files on my harddrive (reiserfs filesystem). I get "permission denied"
> > even if I am the owner or if I try as root. dmesg answers the following
> > for every file (so it's repeated):
> > 
> > is_tree_node: node level 30065 does not match to the expected one 1
> > vs-5150: search_by_key: invalid format found in block 2554621. Fsck?
> > vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to
> > find stat data of [1000086 2592 0x0 SD]
> > 
> > I rebuilt my filesystem with reiserfsck (3.6.11) and it worked, I could
> > read and write again these files. but soon after the rebuilt some other
> > files (they were not concerned by this problem before) appeared to have
> > the same problem and their number kept growing until I rebuilt again the
> > filesystem ... but again new ones appeared after an hour or two ...
> 
> Last time I had a box with similar problems it was memory.  I'd put
> your system through a memtest.

thanks for your answer.
I did as you said but no problem (memtest 3.0).
Some more info on the problem:
- file that appeared to be "access denied" are not the files I had been
using. I did not write or read them for some time.
- As I looked at the Changelogs and the changes that provoke this error
could be in test4, test5, test6, since test3 was fine.
- I first noticed the problem when I used cvs to mirror the repository
of mozilla. my entire partition was unusable afterward (I had to rebuild
everything even the super block). note that the problem appeared later
also on another partition (why / when ? I don't know) that I had not
rebuilt at all so it's not related to the rebuilding.

regards



  parent reply	other threads:[~2003-11-11 17:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 12:19 reiserfs 3.6 problem with test9 Philippe
2003-11-11 13:59 ` Ragnar Hojland Espinosa
2003-11-11 15:05   ` Re[2]: " Maciej Freudenheim
2003-11-11 17:33   ` Philippe [this message]
2003-11-12 10:36   ` Philippe
2003-11-11 16:59 ` bill davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-11-12 14:45 Samium Gromoff
2003-11-12 18:51 ` Philippe
2003-11-12 22:35   ` Oleg Drokin

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=1068572036.344.8.camel@Genesyme \
    --to=rouquier.p@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ragnar@linalco.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