From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Vladimir V. Saveliev" Subject: Re: Filesystem corruption Date: Tue, 29 May 2007 12:15:47 +0400 Message-ID: <200705291215.48354.vs@namesys.com> References: <46598532.5060505@lncsa.com> <465BA9AC.8040805@ultraviolet.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <465BA9AC.8040805@ultraviolet.org> Content-Disposition: inline List-Id: Content-Type: text/plain; charset="us-ascii" To: Tracy R Reed Cc: Laurent CARON , reiserfs-list@namesys.com Hello On Tuesday 29 May 2007 08:18, Tracy R Reed wrote: > Laurent CARON wrote: > > Seems to me it is a filesystem corruption. > > Did I miss it or did not a single person ask you if this happened with > reiserfs 3 or 4? > Laurent mentioned rebuild-tree mode of reiserfsck. So the problem happened with reiserfs 3. > I would be quite surprised if this were reiser 3 and not so surprised if > it were reiser 4 which is still beta afaik. > > Reiser has a nasty reputation for filesystem corruption more than any > other fs. I have always found reiser3 to be rock solid but you can't > mention using reiserfs in mixed company without someone accusing you of > throwing your data away. 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. >