Summary: | sys-fs/unionfs-1.1.3: kernel oops | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Christian Andreetta (RETIRED) <satya> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | kernel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2006-03-05 04:31:41 UTC
there is a similar discussion in the upstream developer list: the cause seems to be an invalid mount sequence. What is the directory layout and the command(s) to unionfs mount? n22 ~ # ls -ld /usr/src/linux-2.6.15-gentoo-r1 ./union* drwxr-xr-x 2 root root 4096 Mar 5 12:42 ./union drwxr-xr-x 2 root root 4096 Mar 5 13:23 ./union_overlay drwxr-xr-x 20 root root 4096 Mar 6 10:19 /usr/src/linux-2.6.15-gentoo-r1 n22 ~ # mount -t unionfs -o dirs=/usr/src/linux-2.6.15-gentoo-r1=ro:/root/union_overlay=rw unionfs /root/union mount: wrong fs type, bad option, bad superblock on unionfs, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so n22 ~ # lsmod | grep union unionfs 62108 0 /dev/hda9 on / type ext3 (rw,noatime) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) udev on /dev type tmpfs (rw,nosuid) devpts on /dev/pts type devpts (rw) shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev) /dev/hda6 on /mnt/F type vfat (rw,noexec,nosuid,nodev,uid=1000,gid=100,umask=0027) usbfs on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85) //ehngsa.ibm.com/ on /mnt/GSA type cifs (rw,mand,noexec,nosuid,nodev) Than 1-5 min later the kernel oopsed - note that the fs wasn't mounted. looks like it is being discussed upstream in these days. kernel<=2.6.15 or unionfs<=1.1.2 don't seem to have issues. I had the same problem a few days ago. Same error, same oops after a few minutes. After looking into unionfs sources, it seems that the first directory after -dirs needs to be rw. So "mount -t unionfs -o dirs=/usr/src/linux-2.6.15-gentoo-r1=ro:/root/union_overlay=rw unionfs /root/union" should be: "mount -t unionfs -o dirs=/root/union_overlay=rw:/usr/src/linux-2.6.15-gentoo-r1=ro unionfs /root/union" If I gived the right parameters to unionfs I did nou experienced any more opps. You're almost right :-) : the sequence is left-most priority based, but the kernel should not block this way. "Almost" because, at the very worst, it should not give you write permission over a file in the left (so, r/o) branch. I'm quite sure it could be done in the past, for example to permit overwrites only to selected files. Maybe it has something to do with the new mutex VFS lock method in kernel sources. (bug #127073). Closing as UPSTREAM for now. reopen if needed |