linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
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 14:43:22 +0200	[thread overview]
Message-ID: <20110509124322.GB306@bitwizard.nl> (raw)
In-Reply-To: <20110509120608.GK4122@quack.suse.cz>

On Mon, May 09, 2011 at 02:06:08PM +0200, Jan Kara wrote:
> > e2fsprogs' mkfs is really missing a check whether any known
> > filesystem/partition type/container (luks, lvm, mdadm, etc.) is already on
> > device (and a -force switch),... IIRC xfsprogs already do this more or
> > less.

>   Yes, that would be reasonable although it might break some
>   people's scripts. But probably worth it anyway.

This is a difficult change.... 

Some GUI install things already perform this check and after asking
confirmation from the user will just execute:

	mkfs.ext3 /dev/....

and expect it to make the filesystem. 

So you could add an option: 
	--check _for_existing_filesystem

But then it is quite likely that people running it manually will
forget to add the option....

	Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  reply	other threads:[~2011-05-09 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <031c613316176c32f09748706a086be2@imap.dd24.net>
2011-05-07  7:38 ` mounting ext3 with another superblock doesn't work? Amir G.
2011-05-07  7:59   ` Yongqiang Yang
     [not found] ` <23AF51ED-8130-4401-94FE-93CF36E8E1C1@dilger.ca>
2011-05-07 22:03   ` Christoph Anton Mitterer
2011-05-09 12:06     ` Jan Kara
2011-05-09 12:43       ` Rogier Wolff [this message]
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

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=20110509124322.GB306@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --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).