that is, briefly, the initrd process, + mkdir -p /lnet/image + mount -n -t ext3 -o ro,noatime /dev/sda1 /lnet/image + mount -n -t tmpfs tmpfs /root/lnet + mkdir -p /cow + mount -n -t tmpfs -o rw,noatime,size=2061756k tmpfs /cow + mkdir -p /xino + mount -n -t tmpfs tmpfs /xino + mount -n -t aufs -o nodev,noatime,nowarn_perm,xino=/xino/.aufs.xino,br:/cow=rw aufs /root + losetup /dev/loop0 /lnet/image/JPLiveLXDE64/00filesystem.squashfs + mount -n -o remount,add:1://root/lnet/00filesystem.squashfs=rr aufs /root + losetup /dev/loop1 /lnet/image/JPLiveLXDE64/10tws.squashfs + mount -n -o remount,add:1://root/lnet/10tws.squashfs=rr aufs /root + mount -n -t squashfs -o ro,noatime /lnet/image/JPLiveLXDE64/90pcjordi.squashfs /root/lnet/90pcjordi.squashfs + mount -n -o remount,add:1://root/lnet/90pcjordi.squashfs=rr aufs /root + mkdir -p /root/lnet/cow + mount -n -o move /cow /root/lnet/cow + mkdir -p /root/lnet/xino + mount -n -o move /xino /root/lnet/xino + mkdir -p /root/lnet/image + mount -o move /lnet/image /root/lnet/image + mount -n -o move /sys /root/sys + mount -n -o move /proc /root/proc ..init the system to /root ...
could be that the mount process does not track correctly the change of the system root directory? El Tuesday 24 March 2009 11:50:48 Jordi Pujol va escriure: > Hello, Junjiro and list, > > I do not know if it is a problem of aufs, but it can be and I expose the > problem in this list > > I am using the new kernel sidux-amd64 2.6.29-0.slh.1 in a Live system, > This kernel has aufs2 integrated (non-module) and squasfs 4.0 (module), > > the file system mounting is as follows: > # mount > tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) > proc on /proc type proc (rw,noexec,nosuid,nodev) > sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) > procbususb on /proc/bus/usb type usbfs (rw) > udev on /dev type tmpfs (rw,mode=0755) > tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) > devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) > rootfs on / type rootfs (rw) > /dev/sda1 on /lnet/image type ext3 > (ro,noatime,errors=continue,data=ordered) tmpfs on /lnet/cow type tmpfs > (rw,noatime,size=2061756k) > tmpfs on /lnet/xino type tmpfs (rw) > tmpfs on /lnet/uloop type tmpfs (rw,size=2061756k) > /dev/loop0 on /lnet/00filesystem.squashfs type squashfs (ro,noatime) > /dev/loop1 on /lnet/10tws.squashfs type squashfs (ro,noatime) > /dev/loop2 on /lnet/90pcjordi.squashfs type squashfs (ro,noatime) > /dev/sda6 on /home type reiserfs (rw,noatime) > /dev/sda2 on /media/winxp type ntfs > (ro,noexec,nosuid,nodev,dmask=0022,fmask=0133,nls=utf8) > /dev/sda5 on /media/windows type vfat > (rw,noexec,nosuid,nodev,iocharset=cp850,utf8,quiet,umask=000,shortname=lowe >r) /home/JPLive/cacheapt-amd64 on /var/cache/apt type none (rw,bind) > /home/JPLive/libapt-amd64 on /var/lib/apt type none (rw,bind) > /dev on /tmp/live-net-remaster-prohO3/chroot/dev type none (rw,bind) > /dev/pts on /tmp/live-net-remaster-prohO3/chroot/dev/pts type none > (rw,bind) > > when executing the remount command in the mount point, the system answers: > # mount -o remount,rw /lnet/image > Killed. > > can see a dump in / var/log/messages, that is attached > > and when executing the remount in the device, it works: > # mount -v -o remount,rw /dev/sda1 > /dev/sda1 on /lnet/image type ext3 > (rw,noatime,errors=continue,data=ordered) > > to verify, issue a mount command: > # mount > /dev/sda1 on /lnet/image type ext3 > (rw,noatime,errors=continue,data=ordered) > > Can you say an opinion about where the problem can be, > > Thanks in advance, > > Jordi Pujol ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
