public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe <rouquier.p@wanadoo.fr>
To: bill davidsen <davidsen@tmr.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs 3.6 problem with test9
Date: Wed, 12 Nov 2003 11:36:03 +0100	[thread overview]
Message-ID: <1068633363.1197.19.camel@Genesyme> (raw)
In-Reply-To: <20031111135948.GA5229@linalco.com>

> Just as a data point, have you tried simply unmounting and remounting
> the f/s? 

Mounting and unmounting is done every time I boot my computer, that is every
day. I haven't seen any error message so far with fsck. 
Maybe I haven't understood what you meant.

If the fsck found anything wrong then I didn't say that, but if
> there were no reported errors in the actual f/s then it is possible that
> the metadata in memory is being corrupted. 

The errors I mentionned are the same every time on the same files.
I get them whenever I check for corrupted files with find / -name klqsjdfhkjlsdfh.
Of course I don't have any file with this name but find write on stdout all files 
it could not access in the system.

which metadata are you talking about? The one in memory or those on the disk?
I check the memory with memtest (no problem) and the disk with badblocks (no problem)
and rebuilt the SB and the FS so there shouldn't be any problem with metadata.

Sorry if I sound stupid but I don't know anything about all that. I'm at loss about what
to do and even think about switchin between reiserfs and ext3.

regards



  parent reply	other threads:[~2003-11-12 10:31 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
2003-11-12 10:36   ` Philippe [this message]
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=1068633363.1197.19.camel@Genesyme \
    --to=rouquier.p@wanadoo.fr \
    --cc=davidsen@tmr.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