From: Szakacsits Szabolcs <szaka@sienet.hu>
To: Kenichi Okuyama <okuyamak@dd.iij4u.or.jp>
Cc: erik@harddisk-recovery.com, reiser@namesys.com,
adilger@clusterfs.com, fs@ercist.iscas.ac.cn,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
zhiming@admin.iscas.ac.cn, qufuping@ercist.iscas.ac.cn,
madsys@ercist.iscas.ac.cn, xuh@nttdata.com.cn,
koichi@intellilink.co.jp, kuroiwaj@intellilink.co.jp,
matsui_v@valinux.co.jp, kikuchi_v@valinux.co.jp,
fernando@intellilink.co.jp, kskmori@intellilink.co.jp,
takenakak@intellilink.co.jp, yamaguchi@intellilink.co.jp,
ext2-devel@lists.sourceforge.net, shaggy@austin.ibm.com,
xfs-masters@oss.sgi.com, Reiserfs-Dev@namesys.com
Subject: Re: [RFD] FS behavior (I/O failure) in kernel summit
Date: Tue, 14 Jun 2005 23:17:22 +0300 (MET DST) [thread overview]
Message-ID: <Pine.LNX.4.61.0506142230460.8028@dhcppc0> (raw)
In-Reply-To: <20050615.021626.42934687.okuyamak@dd.iij4u.or.jp>
On Wed, 15 Jun 2005, Kenichi Okuyama wrote:
>>>>>> "Eric" == Erik Mouw <erik@harddisk-recovery.com> writes:
> Eric> I'd rather have a filesystem which I can tell to warn me immediately
> Eric> about a problem and not make things worse by trying to continue.
> Eric> A mount option for Reiserfs like Andreas proposed would be a good idea.
>
> I 100% agree with you about how file system should act.
There are permanent and transient errors.
Removing a device is ENODEV and I think this is not closely related to any
filesystem. Only Windows seems to detect this properly (the error messages
are perhaps mistranslated by cygwin?)
If the device hits bad sectors then NTFS adds them to the $BadClust list
on-the-fly and won't try to use them anymore, users don't notice anything
unless asked. _Some_ bad sectors don't mean the disk is dying: not all
disks have reserved zone, remapping or it's too small, etc. Many people
use NTFS having defected sectors without issues and no new ones develop
in time.
Thanks for your work. I think it's is important.
Cheers,
Szaka
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-06-14 20:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 19:53 [RFD] FS behavior (I/O failure) in kernel summit fs
2005-06-13 17:59 ` Hans Reiser
2005-06-13 20:13 ` [Ext2-devel] " Andreas Dilger
2005-06-13 23:56 ` Hans Reiser
2005-06-14 2:46 ` Kenichi Okuyama
2005-06-15 14:01 ` [Ext2-devel] " Theodore Ts'o
2005-06-15 19:40 ` Kenichi Okuyama
2005-06-15 20:37 ` [Ext2-devel] " Theodore Ts'o
2005-06-15 20:38 ` Hans Reiser
2005-06-15 22:53 ` Theodore Ts'o
2005-06-16 19:08 ` [Ext2-devel] " Hans Reiser
2005-06-16 11:52 ` Helge Hafting
2005-06-16 19:52 ` Hans Reiser
2005-06-16 21:27 ` Pavel Machek
2005-06-16 11:38 ` Matthew Wilcox
2005-06-14 12:51 ` Erik Mouw
2005-06-14 13:48 ` Denis Vlasenko
2005-06-14 17:16 ` Kenichi Okuyama
2005-06-14 20:17 ` Szakacsits Szabolcs [this message]
2005-06-14 3:46 ` Valdis.Kletnieks
2005-06-14 17:41 ` [Ext2-devel] " fs
2005-06-13 21:51 ` Jeff Mahoney
2005-06-14 0:03 ` Hans Reiser
2005-06-15 17:39 ` Jeff Mahoney
2005-06-16 2:18 ` Dave Chinner
2005-06-16 15:21 ` Jeff Mahoney
2005-06-16 18:52 ` Hans Reiser
2005-06-14 13:22 ` Dave Kleikamp
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=Pine.LNX.4.61.0506142230460.8028@dhcppc0 \
--to=szaka@sienet.hu \
--cc=Reiserfs-Dev@namesys.com \
--cc=adilger@clusterfs.com \
--cc=erik@harddisk-recovery.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fernando@intellilink.co.jp \
--cc=fs@ercist.iscas.ac.cn \
--cc=kikuchi_v@valinux.co.jp \
--cc=koichi@intellilink.co.jp \
--cc=kskmori@intellilink.co.jp \
--cc=kuroiwaj@intellilink.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madsys@ercist.iscas.ac.cn \
--cc=matsui_v@valinux.co.jp \
--cc=okuyamak@dd.iij4u.or.jp \
--cc=qufuping@ercist.iscas.ac.cn \
--cc=reiser@namesys.com \
--cc=shaggy@austin.ibm.com \
--cc=takenakak@intellilink.co.jp \
--cc=xfs-masters@oss.sgi.com \
--cc=xuh@nttdata.com.cn \
--cc=yamaguchi@intellilink.co.jp \
--cc=zhiming@admin.iscas.ac.cn \
/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;
as well as URLs for NNTP newsgroup(s).