Re: resize2fs: Either the superblock or the partition table is likely to be corrupt!
On 2009-07-21 00:21, Sven Joachim wrote:
On 2009-07-21 05:50 +0200, Ron Johnson wrote:
On 2009-07-20 21:29, Manoj Srivastava wrote:
/dev/sda1 /boot ext3 noatime,rw,defaults,noauto 0 2
There is no need to mount /boot unless you install new kernels or update
your bootloader configuration.
Many people prefer to mount it
/dev/mapper/anzu_main-usr_lv /usr ext3 noatime,ro,defaults 0 2
I understand why this is ro; why then is /boot rw?
As I said, Manoj probably only mounts /boot to install new kernels, and
then he wants to write to it.
/dev/mapper/anzu_main-home_lv /home ext3 noatime,rw,nosuid,nodev 0 2
What does nodev mean? (My google fu must be lacking.) Is "Do not
interpret character or block special devices on the file system." just
extra security so that a rogue app doesn't try to create a device file
anywhere but /dev?
It does not prevent _creating_ device files, but it prevent _accessing_
them and the underlying hardware.
Guess I'll be adding that to /home's fstab entry...
/dev/mapper/anzu_main-ulocal_lv /usr/local ext3 noatime,rw,nosuid,nodev 0 2
/dev/mapper/anzu_main-var_lv /var ext3 noatime,rw,nosuid 0 2
/dev/mapper/anzu_main-spool_lv /var/spool ext3 noatime,rw,nosuid,nodev 0 2
Seems to me that this whole exercise is to ensure that /dev is in it's
Hardly, /dev is always on a tmpfs these days. Unless you make your life
hard by not using udev, that is.
Then still I don't see the real gain to separating /usr and
/usr/local into their own partitions.
Scooty Puff, Sr