(initramfs) How to access rw-part after switch_root ?

2013-05-13 Thread paulbg
Hi there Iam quite new to aufs but I managed to get my gentoo boot a squashfs.img into aufs-ro and aufs-rw. My system boots successfuly but how can I access the rw-dir I defined in the initramfs after switch_root? ### init # ...pre-stuff ... # mount the usb

Re: (initramfs) How to access rw-part after switch_root ?

2013-05-13 Thread Sam Liddicott
You should probably save it with a bind mount before cleanup: mkdir -p /mnt/root/rw mount -o bind /mnt/tmpfs/rw /mnt/root/rw then after the switch-root you can look in /rw to find all the modifications that have been made On Mon, May 13, 2013 at 9:43 AM, [1]pau...@gmx.net

Aw: Re: (initramfs) How to access rw-part after switch_root ?

2013-05-13 Thread paulbg
This worked like a charm. Thank you very much :) Gesendet: Montag, 13. Mai 2013 um 11:07 Uhr Von: Sam Liddicott s...@liddicott.com An: pau...@gmx.net Cc: aufs-users aufs-users@lists.sourceforge.net Betreff: Re: (initramfs) How to access rw-part after switch_root ? You should

Re: I/O Error, i46 exists on a upper branch but not pseudo-linked

2013-05-13 Thread sfjro
Hi, Thank you for additional info. Francois Goudal: You can find below all the strace related to /var/spool while starting=20 squid, up to the error caused by aufs : root@wheezy:~# strace squid -D -YC -N 21 | grep spool ::: open(/var/spool/squid/swap.state,=20

Re: I/O Error, i46 exists on a upper branch but not pseudo-linked

2013-05-13 Thread Francois Goudal
Le 13/05/13 15:32, sf...@users.sourceforge.net a écrit : Hi, Thank you for additional info. Francois Goudal: You can find below all the strace related to /var/spool while starting=20 squid, up to the error caused by aufs : root@wheezy:~# strace squid -D -YC -N 21 | grep spool :::

Re: I/O Error, i46 exists on a upper branch but not pseudo-linked

2013-05-13 Thread sfjro
Francois Goudal: I would try, but I have tried to find that sticky bit, but can't find it = : According to the debug output, the sticky bit is set to your /varram. Your /var is /var(ro) and /varram(rw), right? J. R. Okajima

Re: I/O Error, i46 exists on a upper branch but not pseudo-linked

2013-05-13 Thread Francois Goudal
Le 13/05/13 16:07, sf...@users.sourceforge.net a écrit : Francois Goudal: I would try, but I have tried to find that sticky bit, but can't find it = : According to the debug output, the sticky bit is set to your /varram. Your /var is /var(ro) and /varram(rw), right? J. R. Okajima Ah ok, my

Re: I/O Error, i46 exists on a upper branch but not pseudo-linked

2013-05-13 Thread sfjro
Francois Goudal: I have now updated my init script that is responsible for mounting all=20 the aufs and aufs-related stuff, I do a chmod after I mount the tmpfs to=20 /ramvar and the problem is now gone. Glad to hear that! Thank you very much for your help, much appreciated. Still, I

Re: I/O Error, ... exists on a upper branch but not pseudo-linked

2013-05-13 Thread sfjro
Justin: Please find attached some debug info. But I think the best is if you could try the borked live dvd yourself. ::: This looks a same problem which Francois Goudal reported a few days ago. We found that his problem is related to the sticky bit of the upper RW branch dir, and

Kernel 3.9 noplink problem

2013-05-13 Thread Klaus Knopper
Hi, On Mon, May 06, 2013 at 10:36:02AM +0900, sf...@users.sourceforge.net wrote: o enhancement - the simple linked list for the aufs pseudo-link is restructured, and it becomes a very simple hashed list. Could it be that this simplification broke the noplink mount option in aufs3.9 for