All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Toby Thain <toby@smartgames.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: Filesystem corruption
Date: Wed, 30 May 2007 20:08:45 +0400	[thread overview]
Message-ID: <200705302008.45663.vs@namesys.com> (raw)
In-Reply-To: <1138AFDD-ED08-4390-A418-807A84342AE9@smartgames.ca>

Hello

On Tuesday 29 May 2007 16:36, Toby Thain wrote:
> >>  I have always found reiser3 to be rock solid
> 
> My experienced too, over many server years.
> 
> >> 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 were in past several bad stories when reiserfsck was unable restore filesystems because it was unable to find
reiserfs metadata.
Later we found that sometimes (for unknown (but not likely due to reiserfs problem) reason) partition table changes so that 
beginning of a partition gets shifted by few sectors. So, now, when a user reports that reiserfs metadata disappered from a device completely - recovering a partition table to 
original state makes data available again.

> >> You would think the developers would be doing
> >> more to counter this but I have been following reiserfs for years and
> >> nobody seems to really care all that much.
> >>
> 
> Can't do much about human nature. MySQL suffers from the same  
> baseless poisoned folk wisdom.
> 
> --Toby
> 
> 

  parent reply	other threads:[~2007-05-30 16:08 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 13:18 Filesystem corruption Laurent CARON
2007-05-28 12:23 ` Vladimir V. Saveliev
2007-05-28 14:10   ` Laurent CARON
2007-05-28 17:13     ` Vladimir V. Saveliev
2007-05-28 17:27       ` Laurent CARON
     [not found] ` <Pine.LNX.4.64.0705280025570.10429@sheep.housecafe.de>
2007-05-28 17:31   ` Christian Kujau
2007-05-28 18:16     ` Laurent CARON
2007-05-28 23:19       ` Christian Kujau
2007-05-29  8:39       ` Vladimir V. Saveliev
     [not found] ` <465BA9AC.8040805@ultraviolet.org>
2007-05-29  8:15   ` Vladimir V. Saveliev
2007-05-29 12:36     ` Toby Thain
2007-05-30 13:25       ` David Masover
2007-05-30 16:02         ` Vladimir V. Saveliev
2007-05-30 20:06           ` David Masover
2007-05-30 16:42         ` Toby Thain
2007-05-30 19:42           ` David Masover
2007-05-30 16:08       ` Vladimir V. Saveliev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-03  9:31 Filesystem Corruption Stefan Malte Schumacher
2018-12-03 11:34 ` Qu Wenruo
2018-12-03 16:29 ` remi
2014-10-31  0:29 filesystem corruption Tobias Holst
2014-10-31  1:02 ` Tobias Holst
2014-10-31  2:41   ` Rich Freeman
2014-10-31 17:34     ` Tobias Holst
2014-11-02  4:49       ` Robert White
2014-11-02 21:57         ` Chris Murphy
2014-11-03  3:43           ` Zygo Blaxell
2014-11-03 17:11             ` Chris Murphy
2014-11-04  4:31               ` Zygo Blaxell
2014-11-04  8:25                 ` Duncan
2014-11-04 18:28                 ` Chris Murphy
2014-11-04 21:44                   ` Duncan
2014-11-04 22:19                   ` Robert White
2014-11-04 22:34                   ` Zygo Blaxell
2014-11-03  2:55         ` Tobias Holst
2014-11-03  3:49           ` Robert White
2011-01-03  1:58 Patrick H.
2011-01-03  3:16 ` Neil Brown
     [not found]   ` <4D214B5C.3010103@feystorm.net>
2011-01-03  4:56     ` Neil Brown
2011-01-03  5:05       ` Patrick H.
2011-01-04  5:33         ` NeilBrown
2011-01-04  7:50           ` Patrick H.
2011-01-04 17:31             ` Patrick H.
2011-01-05  1:22               ` Patrick H.
2011-01-05  7:02   ` CoolCold
     [not found]   ` <AANLkTinL_nz58f8rSPuhYvVwGY5jdu1XVkNLC1ky5A65@mail.gmail.com>
2011-01-05 14:28     ` Patrick H.
2011-01-05 15:52       ` Spelic
2011-01-05 15:55         ` Patrick H.
2007-06-06  3:10 Filesystem corruption Xu CanHao
2007-06-06 12:16 ` Ingo Bormuth
2007-05-30 20:13 devsk
2007-05-30 17:22 devsk
2007-05-30 19:24 ` Toby Thain
2007-05-30 20:03 ` David Masover
2007-05-31  0:11   ` Ingo Bormuth
2007-06-02 23:10     ` Edward Shishkin
2007-06-04  2:55       ` Ingo Bormuth
2007-06-04  9:41         ` Edward Shishkin
2007-06-05 23:20           ` Ingo Bormuth
2003-08-13 16:05 Locke
2003-08-14  7:49 ` Oleg Drokin
2002-09-05 15:57 Filesystem Corruption Brian Tinsley
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-07  7:15 ` Oleg Drokin
2002-06-11 16:49   ` Kurt
2001-02-05 16:00 Filesystem corruption Ian Chilton
2001-02-05 13:16 Ian Chilton
2001-01-31 14:20 Carsten Langgaard
2001-01-31 15:52 ` Florian Lohoff
2001-01-31 16:24   ` Carsten Langgaard
2001-01-31 16:48     ` Florian Lohoff
2001-02-05 10:02 ` Ralf Baechle
2001-02-05 12:10   ` Alan Cox
2001-02-05 12:10     ` Alan Cox
2001-02-05 12:56     ` Geert Uytterhoeven
2001-02-05 13:01       ` Alan Cox
2001-02-05 13:01         ` Alan Cox
2001-02-05 22:01         ` Ralf Baechle
2001-02-05 22:01           ` Ralf Baechle

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=200705302008.45663.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=toby@smartgames.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.