I've noticed the same thing, with the identical configuration you have. The
reason that the init scripts run swapon twice is in case you are using any
swap _files_, they need to be turned on after all the filesystems have been
mounted. You can either disable the second "swapon", or do as you say (which
I was going to do as well) and figure out why swapon can't tell that the
partition is already enabled.
----- Original Message -----
From: "Eric Sandeen" <sandeen@xxxxxxx>
To: "Glenn Shannon" <glenn@xxxxxxxxxxxx>
Cc: <devfs@xxxxxxxxxxx>
Sent: Tuesday, May 01, 2001 7:11 PM
Subject: Re: swapon -a errors w/ devfs
> Glenn Shannon wrote:
>
> > I run RedHat with DevFS, and I don't see the two swapon entries you are
> > talking about...perhaps it is a different version than the one I use
(6.2
> > with updates).
>
> Yep, this is a shiny 7.1 install w/ devfs.
>
> > However, I used to have a problem with swapon saying that my swap
> > partitions were busy until I re-wrote my fstab (after backing it up of
> > course) to point to the actual devfs names of the partitions.
>
> Ok, I thought that might solve it... but it's another thing to work
> around. I guess maybe I'll dig into swapon to see why it has trouble
> with symlinks...
>
> -Eric
>
> --
> Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
> sandeen@xxxxxxx SGI, Inc.
>
>
>
|