From: "Lukáš Czerner" <lczerner@redhat.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: sandeen@redhat.com, xfs@oss.sgi.com,
"Karel Zak" <kzak@redhat.com>, "Zach Brown" <zabrown@redhat.com>,
"Lukáš Czerner" <lczerner@redhat.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] xfs_mkfs: wipe old signatures from the device
Date: Thu, 14 Feb 2013 09:36:38 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1302140929570.2315@(none)> (raw)
In-Reply-To: <982B8DBB-3FBA-4213-BC92-848A64C60110@colorremedies.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1580 bytes --]
On Thu, 14 Feb 2013, Chris Murphy wrote:
> Date: Thu, 14 Feb 2013 00:29:59 -0700
> From: Chris Murphy <lists@colorremedies.com>
> To: Dave Chinner <david@fromorbit.com>
> Cc: Karel Zak <kzak@redhat.com>, Lukáš Czerner <lczerner@redhat.com>,
> xfs@oss.sgi.com, sandeen@redhat.com, Zach Brown <zabrown@redhat.com>,
> linux-btrfs@vger.kernel.org
> Subject: Re: [PATCH] xfs_mkfs: wipe old signatures from the device
>
>
> On Feb 13, 2013, at 3:17 PM, Dave Chinner <david@fromorbit.com> wrote:
> > it is the responsibility of filesystem
> > tools to behave sanely, not for the rest of the world to have to
> > work around the dangerous behaviour of a specific filesystems'
> > toolset.
>
> I appreciate this, and in particular that mkfs.xfs doesn't nerf a file system without the use of -f; even an existing XFS file system. Considering most data loss is user induced, I'd appreciate it if other file systems's tools weren't so easily made belligerent by (hopefully temporarily) confused apes wearing pants.
>
> Chris Murphy
I would not be so optimistic about it. The reason being that there
are almost _always_ old file system signatures on the device. So I
think that it got to the point where users will usually use mkfs.xfs
-f all the time. And even if they did not and they would use a wrong
device they would probably get the same warning even for the device
they wanted to use in the first place.
So even thoug it might help in some cases I do not think that we
should go and change all file systems to do that as well, it would
not be very useful anyway.
-Lukas
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-14 8:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 11:06 [PATCH] xfs_mkfs: wipe old signatures from the device Lukas Czerner
2013-02-12 11:31 ` Karel Zak
2013-02-12 11:58 ` Lukáš Czerner
2013-02-12 20:27 ` Dave Chinner
2013-02-13 8:01 ` Karel Zak
2013-02-13 10:41 ` Lukáš Czerner
2013-02-13 12:16 ` Karel Zak
2013-02-13 22:17 ` Dave Chinner
2013-02-14 7:29 ` Chris Murphy
2013-02-14 8:36 ` Lukáš Czerner [this message]
2013-02-14 11:04 ` Dave Chinner
2013-02-14 12:28 ` Lukáš Czerner
2013-02-14 14:48 ` Martin Steigerwald
2013-02-14 18:35 ` Eric Sandeen
2013-02-14 14:54 ` Hugo Mills
2013-02-14 17:25 ` Eric Sandeen
2013-02-14 19:08 ` Chris Murphy
2013-02-14 11:45 ` Dave Howorth
2013-02-14 19:17 ` Eric Sandeen
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='alpine.LFD.2.00.1302140929570.2315@(none)' \
--to=lczerner@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
--cc=zabrown@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox