[Unionfs] Kernelpanic after trying to mount a union (2.6.16-ck1, unionfs-20060321-0427)

[Josef Sipek]

On Tue, Mar 21, 2006 at 01:44:33PM +0100, Ferdinand Hübner wrote:
> If I try to
> 
> mount -t unionfs -o dirs=/mnt/hdb1=ro:/mnt/hda7=ro unionfs /data/

You want both directories to be read-only? You should have at least the
highest priority branch rw. If you want the whole union to be ro, make
the highest priority branch rw, but make the mount ro. Eg.

mount -t unionfs -o ro,dirs=/mnt/hdb1=rw:/mnt/hda7=ro unionfs /data/

> unionfs_read_super: error while parsing options (err = -22)

Yeah, that's expected. -22 = Invalid argument

> After about 30 seconds, I get a kernelpanic and my whole system locks
> up. The lockup only happens when I try to get the union to work, so it's
> not related to something different.

That's a known bug, that should get fixed up soon. The problem shows up
whenever the mount fails - if you give it nonexistant directories to
union, etc.

Jeff Sipek.