From: equi-NoX <equi-NoX@wanadoo.fr>
To: Chris Mason <mason@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs errors with 2.6.5-rc1-mm2
Date: Tue, 06 Apr 2004 15:32:50 +0000 [thread overview]
Message-ID: <1081265570.1636.98.camel@ender.WORKGROUP> (raw)
In-Reply-To: <1081254739.4993.82.camel@watt.suse.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Tue, 2004-04-06 at 12:32, Chris Mason wrote:
> On Tue, 2004-04-06 at 01:11, equi-NoX wrote:
> > oops excuse me :/
> >
> > This is one, I can send you others whether you want.
>
> Ok, you need to grab the latest reiserfsprogs from ftp.namesys.com and
> run reiserfsck.
>
> It's really strange that you've got so many messages about freeing a
> block that is already free for the same two block numbers. Please send
> along the results of the reiserfsck when you're done.
>
> -chris
>
but I have already done that ;)
I ran fsck.reiserfs on 04/01, first I ran
fsck.reiserfs /dev/hdb1
then
fsck.reiserfs --fix-fixable /dev/hdb1
but it said me I had to rebuild tree to fix the errors, so I ran
fsck.reiserfs --rebuild-tree /dev/hdb1
And that's ok now
I discovered those reiserfs errors because I was not able to modify some
datas on my /home (which is /dev/hdb1)
I have other logs with reiserfs errors if you want.
Moreover those errors *disappeared* since I use non-mm 2.6.5-rc3 kernel
equi-NoX
--
hoping helping
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-06 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 5:11 reiserfs errors with 2.6.5-rc1-mm2 equi-NoX
2004-04-06 12:32 ` Chris Mason
2004-04-06 15:32 ` equi-NoX [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 20:31 equi-NoX
2004-04-06 0:13 ` Chris Mason
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=1081265570.1636.98.camel@ender.WORKGROUP \
--to=equi-nox@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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