From: Hugh <hugh@nospam.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs error in 2.4.17-rc1 and rc2
Date: Sat, 22 Dec 2001 09:51:37 +0900 [thread overview]
Message-ID: <3C23D919.9080606@nospam.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
I am the one who started this this thread.
I am very sorry. I found that the machine I had the reiserfs error
was running on the 2.4.17-pre6, not one of those rc1 or rc2.
Beside that, I still have a concern on the security level of the
reiserfs in general. On the linux-kernel list, I see more articles
on the troubles of reiserfs than on the troubles of ext3.
Is ext3 more stabilized by now or is ext3 less used in the linux
community?
Again, my apology for the misinformation in the original article.
Best regards,
Hugh
[-- Attachment #2: Reiserfs error in 2.4.17-rc1 and rc2 --]
[-- Type: message/rfc822, Size: 1227 bytes --]
From: Hugh <hugh@nospam.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Reiserfs error in 2.4.17-rc1 and rc2
Date: Fri, 21 Dec 2001 11:47:17 +0900
Message-ID: <3C22A2B5.3010205@nospam.com>
My linux partitions are all Reiserfs format right now.
I moved from 2.4.17-pre1 to 2.4.17-rc2. On such
During the backup at night, I got a strange error saying
in the line of
".... journaling ... write/buffer ..."
in a plain user's console.
I immediately realized that it is reiserfs related.
There are a lot of reiserfs users, especially in the SuSE
camp. If the kernel has a serious bug related to Reiserfs,
that kernel should be marked as "Don't use".
I went back to 2.4.17-pre1 and trying to do "reiserfsck"
on all my partitions.
BTW, "reiserfsck" on a 36GB SCSI driver takes almost forever.
Is it normal?
I am seriously concerned with the integrity of my data.
Should I switch back to ext2 for my data partition?
Thanks for the information in advance
Best regards,
G. Hugh Song
reply other threads:[~2001-12-22 0:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C23D919.9080606@nospam.com \
--to=hugh@nospam.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