>> Well, you need to either mount -o reload or reboot. > Ah, thanks. > But I cannot see /etc/rc.d/resize_root doing that.
Curious. I wonder why not. I'll have to go digging once I have access to a more recent system. (The most recent I run is 5.2, but I have a login on a 9.1, I think it is, system at work. That machine isn't answering ssh at the moment; I expect to get access to it sometime today.) >> meaning mount -o remount > You mean -o reload as above? Oops, yes. My apologies! >> But I _think_ you can't convert a read/write mount to read-only >> without an unmount, which for the root filesystem means a reboot. > But mount(8) says (regarding -u): > also a file system can be changed from read-only to read-write or > vice versa. An attempt to change from read-write to read-only will > fail if any files on the file system are currently open for writing > unless the -f flag is also specified. Hm! Then either my impression is out of date or it doesn't actually work as documented. Given the trouble you had, I wonder if in this case maybe it's the latter. [another mail] >> Or you can use a normal fsck, let it set the size back down, and >> then resize it again when you're done. > That worked, thanks. Good! > However, trying to mount -u -o reload / resulted in > mount_ffs: /dev/raid0a on /: specified device does not match mounted device > so I needed to reboot again (from single user). That...surprises me. I'd have to dig through the FFS support to have any idea what's behind that. > I still wonder how /etc/rc.d/resize_root handles this. So do I! /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
