Messages in this thread | | | Date | Wed, 28 Apr 2004 00:04:59 +0400 | From | Paul P Komkoff Jr <> | Subject | Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (? |
| |
Replying to viro@parcelfarce.linux.theplanet.co.uk: > On Tue, Apr 27, 2004 at 06:05:34PM +0400, Paul P Komkoff Jr wrote: > > Replying to Grzegorz Kulewski: > > > But it is strange that I need kernel patch even if I have no evms > > > or dm volumes in my system. Can not it be solved in mainstream kernels? > > > Maybe there should be warning in config help temporaily? Maybe even note > > > after option name? > > > > This defect grew up off a disagreement between bdclaim authors and > > evms authors > > Excuse me? The damn thing had found nothing. However, it didn't care > to release the devices it had claimed - hadn't even closed them, as the > matter of fact. That's a clear and obvious bug, regardless of any > disagreements.
As far as I can see from here, evms parsed partition table, called dmsetup several times and created corresponding nodes in /dev/evms.
Thus we allowed to mount /dev/evms/hda1 but /dev/hda1 stopped working. That's why it did not released hda - because it has active devmapper on top.
> Speaking of the proposed "solutions", how about #4: figure out what, > when and for how long do they really want to claim and take care to > release what they don't end up using?
Logic is easy - evms trying to concentrate block device management into its own hands, but we have in-kernel partitioning code to consider ...
> WTF is going on there?
:(
-- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |