I think people just like to spread FUD without doing any analysis of what
really caused the FS corruption. It can be anything from a bad 3rd party driver
to bad hardware ('bad blocks', does anybody check for them before mkfs these
days? I do). People also like to try those untested patchsets, containing every
blah that's thrown out by so called 'kernel hackers' which makes your system
10x faster. Rieser4 seems like an easy candidate to vent their anger on
afterwards.
I have used R4 for a year now and I have had to reset my PC, troubleshooting
problems with vmware/mythtv/cisco vpn client/nvidia, so many times that its not
even funny! And R4 didn't give me any problems even once. It boots right up,
without any files lost and consistent FS as a subsequent livecd boot and fsck
proved it everytime. If I did that to ext or xfs, I would have lost big time.
Only files I have ever lost were on ext3 during a sudden power failure. I don't
trust safety of my data on any FS but Rieserfs. I hope people don't leave this
good piece of code to rot!!
-devsk
----- Original Message ----
From: Toby Thain <[EMAIL PROTECTED]>
To: David Masover <[EMAIL PROTECTED]>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Sent: Wednesday, May 30, 2007 9:42:01 AM
Subject: Re: Filesystem corruption
On 30-May-07, at 10:25 AM, David Masover wrote:
> On Tuesday 29 May 2007 07:36:13 Toby Thain wrote:
>
>>>> but you can't
>>>> mention using reiserfs in mixed company without someone accusing
>>>> you of
>>>> throwing your data away.
>>
>> People who repeat this rarely have any direct experience of Reiser;
>> they repeat what they've heard; like all myths and legends they are
>> transmitted orally rather than based on scientific observation.
>
> Well, there is one problem I vaguely remember that I don't think
> has been
> addressed, I think it was one of those lets-put-it-off-till-v4
> things. It was
> the fact that there are a limited number of inodes (or keys, or
> whatever you
> call a unique file),
But does it cause data loss? One usually sees claims that "reiserfs
ate my data", or "I heard reiserfs ate somebody's data", but without
supplying a root cause - bad memory? powerfail? bad disk? etc.
> and no way of knowing how many you have left until your
> FS will suddenly, one day refuse to create another file.
>
> ... switching away from Reiser4
> means I no longer see random files (including stuff in, for
> example, /sbin,
> that I hadn't touched in months) go up in smoke.
I only wish sanity had prevailed over kernel inclusion, then we'd
see it shaken down a lot quicker, like R3 was.
>
> Ordinarily I like to help debug things, but not at the risk of my
> data. Maybe
> I'll try again later, and see if I can reproduce it in a VM or
> somewhere
> safe...
>
> I do still follow the list, though, in case something interesting
> happens.
Yeah, R4 is "something interesting". :) I still hope it gets finished...
--Toby
> It
> was fun while it lasted!
____________________________________________________________________________________Boardwalk
for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's
economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
