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

[Sven Luther]

On Sat, Oct 16, 2004 at 11:17:25AM +0200, Eduard Bloch wrote:
> #include <hallo.h>
> * Sven Luther [Sat, Oct 16 2004, 11:19:35AM]:
> 
> > Mmm, this is probably a upstream issue, and not likely to be fixed before the
> > sarge release.
> > 
> > I will investigate on monday.
> 
> Okay.
> 
> > Could you give me more details of your setup, when it does happen, and why in
> > hell you are using devfs. Only d-i should be using devfs, and there has be no
> > report of this kind of problem in d-i, but then maybe not many have tried vfat
> > resizing in d-i ?
> 
> Ehm, D-I? Did I say anything about D-I? I was normal operation on a
> normal system. I have hda1 (15GiB, FAT32), and an extended container
> (hda1) with one logical partition (hda5, XFS filesystem, 15GB). I
> umounted hda1 and used parted to resize it to 14.5GiB (to get space for
> a swap partition). Well, and after moving the data, it stoped, as
> 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
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.

But as said, parted is frozen as part of base, so most of this stuff is
post-sarge.

That said, maybe you could try booting the debian-installer, and doing the
resize from it ?

Friendly,

Sven Luther