From: Hans Reiser <reiser@namesys.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
David Weinehall <david@southpole.se>,
Andrew Ho <andrewho@animezone.org>, Dax Kelson <dax@gurulabs.com>,
Peter Nelson <pnelson@andrew.cmu.edu>,
linux-kernel <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net, ext3-users@redhat.com,
jfs-discussion@www-124.southbury.usf.ibm.com,
reiserfs-list@namesys.com, linux-xfs@oss.sgi.com
Subject: Re: Desktop Filesystem Benchmarks in 2.6.3
Date: Wed, 03 Mar 2004 16:42:25 +0300 [thread overview]
Message-ID: <4045E0C1.9020806@namesys.com> (raw)
In-Reply-To: <200403031059.26483.robin.rosenberg.lists@dewire.com>
Robin Rosenberg wrote:
>On Wednesday 03 March 2004 10:43, Felipe Alfaro Solana wrote:
>
>
>>But XFS easily breaks down due to media defects. Once ago I used XFS,
>>but I lost all data on one of my volumes due to a bad block on my hard
>>disk. XFS was unable to recover from the error, and the XFS recovery
>>tools were unable to deal with the error.
>>
>>
>
>What file systems work on defect media?
>
>As for crashed disks I rarely bothered trying to "fix" them anymore. I save
>what I can and restore what's backed up and recovery tools (other than
>the undo-delete ones) usually destroy what's left, but that's not unique to
>XFS. Depending on how good my backups are I sometimes try the recovery
>tools just to see, but that has never helped so far.
>
>-- robin
>
>
>
>
Never attempt to recover without first dd_rescue ing to a good hard
drive, and doing the recovery there on good hard drive.
--
Hans
next prev parent reply other threads:[~2004-03-03 13:42 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 4:46 Desktop Filesystem Benchmarks in 2.6.3 Peter Nelson
2004-03-02 4:46 ` Peter Nelson
2004-03-02 7:23 ` Hans Reiser
2004-03-02 16:34 ` Peter Nelson
2004-03-02 22:33 ` Dax Kelson
2004-03-02 22:47 ` David Weinehall
2004-03-03 1:30 ` Andrew Ho
2004-03-03 1:30 ` Andrew Ho
2004-03-03 1:41 ` David Weinehall
[not found] ` <20040303014115.GP19111@khan.acc.umu.se.suse.lists.linux.kernel>
2004-03-03 2:39 ` Andi Kleen
2004-03-03 7:47 ` Christoph Hellwig
2004-03-03 8:03 ` Hans Reiser
2004-03-03 8:16 ` Arjan van de Ven
2004-03-03 9:35 ` Hans Reiser
2004-03-03 17:29 ` Hubert Chan
2004-03-04 0:10 ` Hans Reiser
2004-03-03 6:00 ` Robin Rosenberg
2004-03-03 9:43 ` Felipe Alfaro Solana
2004-03-03 9:59 ` Robin Rosenberg
2004-03-03 10:19 ` Felipe Alfaro Solana
2004-03-03 10:49 ` Christian Mayrhuber
2004-03-03 10:56 ` Mihai RUSU
2004-03-03 13:58 ` Hans Reiser
2004-03-04 9:28 ` Kristian Köhntopp
2004-03-05 1:59 ` Clemens Schwaighofer
2004-03-05 4:21 ` cami
2004-03-05 20:52 ` Mike Fedyk
2004-03-05 22:30 ` cami
2004-03-07 4:50 ` Mike Fedyk
2004-03-03 10:24 ` Mike Gigante
2004-03-03 10:24 ` Mike Gigante
2004-03-03 13:14 ` Felipe Alfaro Solana
2004-03-03 14:16 ` Hans Reiser
2004-03-03 13:42 ` Hans Reiser [this message]
2004-03-03 10:13 ` Olaf Frączyk
2004-03-03 13:07 ` Felipe Alfaro Solana
2004-03-03 13:07 ` Felipe Alfaro Solana
2004-03-04 14:37 ` [Jfs-discussion] " Pascal Gienger
2004-03-04 20:43 ` Per Andreas Buer
2004-03-03 6:30 ` Hans Reiser
2004-03-03 23:41 ` Johannes Stezenbach
2004-03-05 18:46 ` Pavel Machek
[not found] ` <1078586701.6237.0.camel@redeeman.linux.dk>
2004-03-07 12:15 ` Redeeman
2004-03-16 8:16 ` Vladimir Saveliev
2004-03-06 0:16 ` Chris Mason
2004-03-06 0:16 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 17:11 Ray Lee
2004-03-05 3:32 Burnes, James
2004-03-05 3:48 ` Clemens Schwaighofer
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=4045E0C1.9020806@namesys.com \
--to=reiser@namesys.com \
--cc=andrewho@animezone.org \
--cc=david@southpole.se \
--cc=dax@gurulabs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pnelson@andrew.cmu.edu \
--cc=reiserfs-list@namesys.com \
--cc=robin.rosenberg.lists@dewire.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 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.