sf...@users.sourceforge.net wrote:

> > I think 'is busy' is not what you wanted. Should I try it again
> > slightly modified?
> 
> 'is busy' is the expected error.
> This behaviour is correct, and fsck reports errors very similarly to
> your rsync case. Did your rsync script really succeed remounting
> readonly? Can you confirm it by /proc/mounts or something?

Yes, it is mounted according to /proc/mounts (here is the whole, for
your amusement) :

- - - - - - - -
rootfs / rootfs rw 0 0
/dev/sda1 /mnt/ro_root ext3
ro,relatime,errors=continue,barrier=0,data=writeback 0 0
none /mnt/rw_root tmpfs rw,dirsync,relatime 0 0 none / aufs
rw,relatime,si=807d837c 0 0 proc /proc proc rw,relatime 0 0
rc-svcdir /lib/rc/init.d tmpfs
rw,nosuid,nodev,noexec,relatime,size=1024k,mode=755 0 0 sysfs /sys
sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev tmpfs
rw,nosuid,relatime,size=10240k,mode=755 0 0 devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620 0 0 shm /dev/shm tmpfs
rw,nosuid,nodev,noexec,relatime 0 0 usbfs /proc/bus/usb usbfs
rw,nosuid,noexec,relatime,devgid=85,devmode=664 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
- - - - - - - -

Also, I can run the command later after the script by hand:

- - - - - - - -
nibbler ~ # mount -vo remount,ro /dev/sda1 
/dev/sda1 on /mnt/ro_root type ext3 \
(ro,relatime,errors=continue,barrier=0,data=writeback)
- - - - - - - -

If I try to remount r/w, /var/log/messages prints:

Nov 28 14:59:23 nibbler klogd: EXT3-fs (sda1): warning: couldn't \
remount RDWR because of unprocessed orphan inode list.  Please \
umount/remount instead.



#Marcus

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

Reply via email to