Hmm, I just noticed that the md1 device was commented out in /etc/mdadm/mdadm.conf, but I don't know if that file is auto-generated by the process of assembling the devices.
Anyway, since this is a swap partition we don't need its previous contents. Can we delete and re-create it? On Mon, 2007-07-30 at 08:12 +0200, Anton Xuereb wrote: > On behalf of Dino Conti (He has some problems with the Mailing list > right now) > > > Hi guys, > > Although the SWAP device is listed in FSTAB, it does not get mounted. > > After formatting the partition as SWAP, use the SWAPON command to > activate it. > > > > Please find following output from my running server > > > > [EMAIL PROTECTED] ~]# fdisk -l > > > > Disk /dev/hdg: 20.0 GB, 20020396032 bytes > > 255 heads, 63 sectors/track, 2434 cylinders > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > > Device Boot Start End Blocks Id System > > /dev/hdg1 * 1 2332 18731758+ 83 Linux > > /dev/hdg2 2333 2434 819315 82 Linux swap > > [EMAIL PROTECTED] ~]# mount > > /dev/hdg1 on / type ext3 (rw) > > none on /proc type proc (rw) > > none on /sys type sysfs (rw) > > none on /dev/pts type devpts (rw,gid=5,mode=620) > > usbfs on /proc/bus/usb type usbfs (rw) > > none on /dev/shm type tmpfs (rw) > > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > > /proc on /var/named/chroot/proc type none (rw,bind) > > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) > > [EMAIL PROTECTED] ~]# cat /etc/fstab > > # This file is edited by fstab-sync - see 'man fstab-sync' for details > > LABEL=/ / ext3 defaults > 1 1 > > none /dev/pts devpts gid=5,mode=620 > 0 0 > > none /dev/shm tmpfs defaults > 0 0 > > none /proc proc defaults > 0 0 > > none /sys sysfs defaults > 0 0 > > LABEL=SWAP-hdg2 swap swap defaults > 0 0 > > /dev/hdc /media/cdrecorder auto > pamconsole,exec,noauto,managed 0 0 > > /dev/fd0 /media/floppy auto > pamconsole,exec,noauto,managed 0 0 > > > > > > dino > > > On 7/29/07, Mario Xerri <[EMAIL PROTECTED]> wrote: > > Hi Raphael, > > Let's assess your setup from the ground up. First of all, > post the > contents of /proc/mdstat (the md1 stanza is enough) and the > output of: > mdadm --detail /dev/md1 > > Your raid device might not be configured correctly. > > On Sun, 29 Jul 2007 01:27:11 +0200 > "Raphael Borg Ellul Vincenti" <[EMAIL PROTECTED]> wrote: > > > Yes... mkswap /dev/md1 returns that the device needs to be > at least > > 40K or bigger. > > > > That is probably because since the md1 device is still not > started > > (its only active) then the device is still zero. > > > > starting the raid device says that md1 is still in use > > > > Tracing the output of lsof shows that nobody is using md1 > yet. My > > suspicion is that the system is still thinking that md1 > should be the > > swap device and that is the reason why its still in use. > > > <snip> > > -- > Mario Xerri > [holo] > _______________________________________________ > MLUG-list mailing list > [email protected] > http://mailserv.megabyte.net/mailman/listinfo/mlug-list > > > > _______________________________________________ > MLUG-list mailing list > [email protected] > http://mailserv.megabyte.net/mailman/listinfo/mlug-list Tel: (+356) 21421600 URL: www.megabyte.net Fax: (+356) 21421590 E-mail: [EMAIL PROTECTED] DISCLAIMER The information contained in this electronic mail may be confidential or legally privileged. It is for the intended recipient(s) only. Should you receive this message in error, please notify the sender by replying to this mail. Unauthorised use of the contents is strictly prohibited. Whilst all care has been taken, the Megabyte Group is not responsible for the integrity of the contents of this electronic mail and any attachments included within.
_______________________________________________ MLUG-list mailing list [email protected] http://mailserv.megabyte.net/mailman/listinfo/mlug-list
