hal sometimes creates volumes for raw device and partitions

[Danny Kukawka]

On Friday 21 October 2005 17:51, Martin Pitt wrote:
> Hi hal developers!
>
> With some devices, hal creates a volume node for both the raw device
> (/dev/sda) and the partitions on it (like /dev/sda1). This can be
> produced pretty reliably by mkdosfs'ing the raw device, and then
> partitioning sda and mkdosfs'ing sda1. It seems that the first blocks
> sometimes still have a valid file system signature, despite a valid
> partition table being there as well. This leads to undesired effects
> like invalid drives in gnome-vfs and failed mounts.

Btw. IMO this is also a bug in the partition tools. In the most cases you can 
workaround this if you fill the first 64k with 0 (use dd) and format the 
device new.

> See https://bugzilla.ubuntu.com/show_bug.cgi?id=13140 for details, hal
> debug output, etc.

We have several bugreports about this problem:
https://bugzilla.novell.com/show_bug.cgi?id=115137
https://bugzilla.novell.com/show_bug.cgi?id=115552
https://bugzilla.novell.com/show_bug.cgi?id=127511

I work currently on a solution for this problem.

> Rather than trying to fiddle with drive_id and volume_id, can we
> implement a simple sanity check that does not create a volume for the
> raw device when there are already partition volumes, and removes a raw
> volume as soon as a partition volume arrives?

That's what I planed. Check if create a new volume if there is already a 
volume on the raw device and remove this volume.

Cheers,

Danny