On Sat, May 29, 2010 at 03:16:48AM +0200, Oliver Welter wrote:
> Hi Folks,
> I moved from an old 2.6.22 to a recent kernel last week and now I am
> seeing a lockup issue.
just to clarify, a recent kernel with _additional_ patches
applied (unionfs)?
> My setup is a bit complex: the guest root is build from common a
> read-only root-partiton (basic partition) + guests data (drbd-device),
> joined with unionfs.
> Problem: The unionfs is merged by a prepre-start script, so it is only
> visible in the guest context. After the guest is stopped, I am unable
> to free the drbd device ("device is held open by someone"). Using drbd
> without unionfs works, assembling the unionfs outside the vserver also
> works.
> The new kernel is 2.6.33.4 with recent vServer experimental patchset
> and (another variant) of unionfs
> (http://www.fsl.cs.sunysb.edu/project-unionfs.html).
my guess would be that unionfs somehow doesn't handle the
mounting inside namespaces properly, so I'd suggest to do
the following:
- test without the Linux-VServer patches applied but
within different namespaces
- check that the unionfs patches match the Linux-VServer
ones
> I ran the same setup using "aufs2" with a 2.6.22-vs-2.2.0.7 for
> several years now without major problems.
apples and oranges ... I don't see why it shouldn't work
in general, but unionfs/drbd isn't aufs2 :)
best,
Herbert
> Anybody has some ideas or a working setup with other tools?
> Oliver
> --
> Protect your environment - close windows and adopt a penguin!
> PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
>
Received on Sat May 29 13:09:43 2010