public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: adilger@turbolinux.com, lars@larsshack.org, mikpe@csd.uu.se
Cc: amnet@amnet-comp.com, hch@caldera.de, jjasen1@umbc.edu,
	linux-kernel@vger.kernel.org, util-linux@math.uio.no
Subject: Re: [util-linux] Re: magic device renumbering was -- Re: Linux 2.4.2ac20
Date: Fri, 16 Mar 2001 00:31:07 +0100 (MET)	[thread overview]
Message-ID: <UTC200103152331.AAA2159588.aeb@vlet.cwi.nl> (raw)

> I've implemented a patch for util-linux-2.11a
> which adds LABEL support to mkswap(8) and swapon/swapoff(8).

Yes, maybe a reasonable idea.

But I would prefer a somewhat more ambitious approach.

My first thought was: why label individual swap partitions?
I almost never want to distinguish swap partitions, and just do
"swapon -a". In case one wants to guard against changing device names,
why not add an option -A so that "swapon -A" does swapon on each
partition with a swap signature?

However, that would greatly increase the risk that exists already
today: someone has a swap partition, and does mkfs.foo, and
it so happens that foofs does not use the sector with the swapsignature.
Now this foofs partition has a swap signature, but we would be very
unhappy if it were used as swap space.

The real problem is that our disks usually do not have a volume label.
Outside of all file systems.
The "signatures" that we rely on today are located in different places,
so that a filesystem can have several valid signatures at the same time.
And we first know where to look when we know the type already.

Design a Linux partition table format, where a partition descriptor
has fields start, end, fstype, fslabel, and the whole disk has a vollabel.
Put it in sector 0-N for an all-Linux disk, and in sectors pointed at
by a classical DOS-type partition table entry when the disk is shared.

(Maybe I already did that once - it sounds so familiar now that I write
this. Then why was it not pursued? Maybe LVM already does these things?)

Andries

             reply	other threads:[~2001-03-15 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 23:31 Andries.Brouwer [this message]
2001-03-16  0:51 ` [util-linux] Re: magic device renumbering was -- Re: Linux 2.4.2ac20 Andreas Dilger
2001-03-16 13:57   ` Mikael Pettersson
2001-03-16  1:08 ` Alexander Viro
     [not found] <mng==UTC200103152331.AAA2159588.aeb@vlet.cwi.nl>
2001-03-16  2:37 ` Michail Brzitwa

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=UTC200103152331.AAA2159588.aeb@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=adilger@turbolinux.com \
    --cc=amnet@amnet-comp.com \
    --cc=hch@caldera.de \
    --cc=jjasen1@umbc.edu \
    --cc=lars@larsshack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=util-linux@math.uio.no \
    /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