Just to summarize a bit, so maybe someone gets an idea what is happening.

We currently have a raid device, /dev/md1, that is partitioned as swap
space. However the problem is that we cannot get it online to be used as
swap..the following is /etc/fstab

[EMAIL PROTECTED]:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/md2        /               ext3    defaults,errors=remount-ro 0       0
/dev/md0        /boot           ext3    defaults        0       2
/dev/mapper/VolGroup00-LogVol06 /mirror         ext3    defaults
0       0
/dev/md1        none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0


/dev/md1 was commented out and i removed the comment however after doing a
sudo mount -a, it didnt come up


the current mounted partitions are:

[EMAIL PROTECTED]:~$ mount
/dev/md2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
/dev/mapper/VolGroup00-LogVol06 on /mirror type ext3 (rw)


right after a mount -a. i did in hopes of changing something i did a swapon
-a

the result was:

[EMAIL PROTECTED]:~$ sudo swapon -a
swapon: /dev/md1: Invalid argument


Now this is a plea for help for anyone who might have any ideas...we sorely
need to fix this prob as as soon as someone visits the site, the amount of
ram gets dangerously low.



An idea would be to restart the server and see if the partition is mounted
properly at boot time, however we might risk bricking the server and thus we
would need to revisit the NOC to fix the problem...Not something many of us
feel like doing or have the time to right now


SO..Any ideas??

M
_______________________________________________
MLUG-list mailing list
[email protected]
http://mailserv.megabyte.net/mailman/listinfo/mlug-list

Reply via email to