linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	adilger@dilger.ca, amir73il@users.sourceforge.net
Subject: Re: mounting ext3 with another superblock doesn't work?
Date: Mon, 9 May 2011 09:28:18 -0400	[thread overview]
Message-ID: <20110509132818.GI4138@thunk.org> (raw)
In-Reply-To: <20110509120608.GK4122@quack.suse.cz>

On Mon, May 09, 2011 at 02:06:08PM +0200, Jan Kara wrote:
>   Yes, that would be reasonable although it might break some people's
> scripts. But probably worth it anyway.

I wouldn't object to a patch to e2fsprogs which changes mke2fs to do
this check and refuses to blow away a file system if:

[defaults]
    check_for_prexisting_fs = true

was in /etc/mke2fs.conf.

I'd also suggest that mke2fs -f NOT enable mke2fs to blow away file
systems, but that we add a new utility --- probably to util-linux-ng
--- with the destroy_partition, which a system administrator has to
explicitly run to blow away a partition.

I'd really rather not train people that mke2fs -f is the way to get
the utility to !@#@! shut up.  It's exactly the same problem with why
"alias rm 'rm -i'" doesn't work.  System administrators just get in
the habit of typing return, 'y', return, and in the end things still
just get lost.

If we have a separate utility, destroy_filesystem, which checks to see
if there is a tty, and if so, prints the details of what is on the
partition, and then forces the user to type "YES<return>", then we
have a unified way of protecting against careless sysadmins.  We can
also have that utility do clever things, such as simply telling the
hard drive to reinitiailize its crypto keys if it supports FDE, or
tell it to TRIM the entire disk if it supports TRIM/DISCARD, etc.

							- Ted

      parent reply	other threads:[~2011-05-09 13:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07  0:09 mounting ext3 with another superblock doesn't work? Christoph Anton Mitterer
2011-05-07  5:56 ` Andreas Dilger
2011-05-07 22:03   ` Christoph Anton Mitterer
2011-05-09 12:06     ` Jan Kara
2011-05-09 12:43       ` Rogier Wolff
2011-05-09 12:59       ` Christoph Anton Mitterer
2011-05-09 13:10         ` Jan Kara
2011-05-09 13:47           ` Christoph Anton Mitterer
2011-05-09 14:08             ` Jan Kara
2011-05-09 13:18         ` Lukas Czerner
2011-05-09 13:28       ` Ted Ts'o [this message]

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=20110509132818.GI4138@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=amir73il@users.sourceforge.net \
    --cc=calestyo@scientia.net \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).