mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Pollard <jesse@cats-chateau.net>
To: Alexander Viro <viro@math.psu.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: BERECZ Szabolcs <szabi@inf.elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: mount /dev/hdb2 /usr; swapon /dev/hdb2 keeps flooding
Date: Sun, 13 May 2001 08:04:26 -0500	[thread overview]
Message-ID: <01051308104500.22790@tabby> (raw)
In-Reply-To: <Pine.GSO.4.21.0105121939310.11973-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105121939310.11973-100000@weyl.math.psu.edu>

On Sat, 12 May 2001, Alexander Viro wrote:
>On Sun, 13 May 2001, Alan Cox wrote:
>
>> > > root@kama3:/home/szabi# cat /proc/mounts
>> > > /dev/hdb2 /usr ext2 rw 0 0
>> > > root@kama3:/home/szabi# swapon /dev/hdb2
>> > 
>> > - Doctor, it hurts when I do it!
>> > - Don't do it, then.
>> > 
>> > Just what behaviour had you expected?
>> 
>> EBUSY would be somewhat nicer.
>
>Probably. Try to convince Linus that we need such exclusion. All stuff
>needed to implement it is already there - see blkdev_open() for details.
>OTOH, as long as kernel itself survives that... In this case I can see
>the point in "give them enough rope" approach.

It doesn't matter .... The device is not a swap partition - from the
original message:
> root@kama3:/home/szabi# swapon /dev/hdb2
> set_blocksize: b_count 1, dev ide0(3,66), block 2, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 3, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 4, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 5, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 6, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 7, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 8, from c0126b48
> set_blocksize: b_count 1, dev ide0(3,66), block 1, from c0126b48
> Unable to find swap-space signature
> swapon: /dev/hdb2: Invalid argument

The error message is quite clear (the set blocksize isn't, but that
is during the identification and isn't an error, but appears to be
a status..).

If you are going to swap on a mounted file system, then you have to
specify a swap file, formatted for swap.

The message that was output says exactly what is needed for protecting
against configuration errors.

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: jesse@cats-chateau.net

Any opinions expressed are solely my own.

  reply	other threads:[~2001-05-13 13:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12 23:00 BERECZ Szabolcs
2001-05-12 23:23 ` Alexander Viro
2001-05-12 23:32   ` Alan Cox
2001-05-12 23:42     ` Alexander Viro
2001-05-13 13:04       ` Jesse Pollard [this message]
2001-05-13  0:00     ` Guest section DW
2001-05-12 23:33   ` BERECZ Szabolcs
2001-05-12 23:39     ` Alexander Viro
2001-05-12 23:54       ` BERECZ Szabolcs
2001-05-13 14:21       ` Gerhard Mack
2001-05-13 16:23       ` Alan Cox
2001-05-14  9:29     ` 2.2.19 and RAID levels Riccardo Facchetti
2001-05-14  9:30       ` Alan Cox
2001-05-12 23:25 ` mount /dev/hdb2 /usr; swapon /dev/hdb2 keeps flooding Matthew Dharm
2001-05-12 23:42   ` BERECZ Szabolcs
2001-05-13  2:17 ` ashridah

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=01051308104500.22790@tabby \
    --to=jesse@cats-chateau.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szabi@inf.elte.hu \
    --cc=viro@math.psu.edu \
    /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

all inboxes | Powered by JetHome®