[Parted-maintainers] Bug#276721: tries to open non-existing device files and hangs

[Sven Luther]

On Sat, Oct 16, 2004 at 01:16:35PM +0200, Eduard Bloch wrote:
> #include <hallo.h>
> * Sven Luther [Sat, Oct 16 2004, 01:15:56PM]:
> 
> > > described. After I have created the device nodes part1...16 manually in
> > > /dev/ide/..., it was ready in few seconds. So it did really hang on this
> > > position, trying to open device nodes that did not exist and failing. I
> > > expect exactly the same problem on other /dev directories where only
> > > device nodes for existing partitions are created.
> > 
> > So, if you are trying to format /dev/hda1 or resize it or whatever, so why in
> > hell are you trying to setup the devfs disk devices ? I also think this is
> 
> ??
> 
> I did not try to setup any new devfs related thing. I was just *using*
> devfs, all the time.

You should not use evil devfs at all. :)

Seriously, it is going to be removed from the 2.6 kernels very soon, and you
should maybe try using udev instead.

What confused me is you speaking of /dev/hda1. Are you sure you have the devfs
stuff ? What kernels are you using anyway ?

> > related to some problem with the resize design that was spoken of in the
> > parted mailing list. I will follow up on this. Basically, if i understood
> > well, when resizing, libparted is syncing all the partitions, and then
> > reopening it, or something such.
> 
> Something like that. Maybe it tried to open the "new" partition, which
> did not exist because the kernel was not able to reread the part. table,
> and then it started to wreak random havoc. Just a theory.

Did you get any message about rereading the partition table ? 

> > But as said, parted is frozen as part of base, so most of this stuff is
> > post-sarge.
> 
> That is why such long freeze phase sucks.

Well, since only base is frozen, it is not as problematic. Now, the real
problem is that there was an API change of libparted, so we cannot just reuse
the newer version.

> > That said, maybe you could try booting the debian-installer, and doing the
> > resize from it ?
> 
> I could, but not yet. And if my assumption above is correct, it will
> work because on the installer, nothing is mounted so the kernel will
> reread the partition table cleanly and create the new device file.

Err, are you trying to modify a partition while it is mounted ? This is _NOT_
supposed to happen. But please give d-i it a try anyway, it is best to have
fact and not assumptions when tracking stuff like that. I cannot really help
you all that much myself, since i don't use devfs, have no 2.4 kernel anymore,
and anyway don't have any disk with a MBR or a fat partition on it anyway.

Friendly,

Sven Luther