At Mon, 28 Feb 2005 03:48:00 +0100, Goswin von Brederlow wrote: > GOTO Masanori <[EMAIL PROTECTED]> writes: > > At Sat, 26 Feb 2005 14:40:33 +0100, > > Goswin Brederlow wrote: > >> when one tries to run pvmove or lvsnapshot on / the lvm will deadlock > >> itself due to atime updates on /dev/ being blocked while the LVM is > >> locked. Sine any read/write access to / will be blocked the system > >> breaks. > >> > >> To prevent this lvm uses O_NOATIME where available, which is still not > >> the case in current linux-kernel-headers. > > > > I couldn't understand why this problem is occured. O_NOATIME was > > introduced in 2.6.7. Is the root of problem to upgrading lvm package? > > Bastian's patch adds only O_NOATIME flag - this means that lvm can fix > > using O_NOATIME in your new package. In other words, lvm is > > "severity: critical", but glibc is not. lvm is kernel related > > package, so depending on libc6 header sometimes causes problems. > > The docs (man 2 open) document O_NOATIME but the headers are lacking > behind in carrying the implementation. So you got stuck with it as > primary package. Notice that lvm2 is secondary. If lvm adds a > workaround the priority drops but you are still missing documented > behaviour, behaviour the sarge kernel (2.6.8) has.
> Bastian's patch is just a workaround around the bug not its solution. ...So why did you submit this bug as "severity: critical" assigned to linux-kernel-header? What the real solution to fix this report? Can your problem be fixed to define O_NOATIME in lvm2 or linux-kernel-headers package? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
