* Marco d'Itri ([EMAIL PROTECTED]) wrote: > On Sep 20, Stephen Frost <[EMAIL PROTECTED]> wrote: > > dpkg: error processing udev (--configure): > > subprocess post-installation script returned error exit status 1 > Did you try to kill some process? I can't see how an error could be > propagated from vol_id to postinst.
Nope, I didn't kill any processes. It took it a while to fail. In case
it gets lost in irc:
12:10 <Snow-Man> Md: It's in the bug log
12:11 <Snow-Man> Md: Basically, vol_id was failing.
12:11 <Snow-Man> 'cause it was trying to read the device, and the device
was, like, 'uh, no.'
12:11 <Snow-Man> I didn't kill off any processes, no...
12:12 <Snow-Man> Md: Well, alright, vol_id was the process which was
running when I was seeing
stuff in dmesg show up (the stuff that's in the bug
log)
12:12 <Snow-Man> Md: It's possible there was some other issue making
udevstart fail..
12:13 <Snow-Man> Md: But when I enabled the snapshots, I saw vol_id go
past the first set of things
it was being run on.
12:13 <Snow-Man> (--export /tmp/udev.gzcWTS/.tmp-8-32 went to, like,
8-16, etc, iirc)
12:14 <Snow-Man> It looked like udevstart was running vol_id multiple
times, and checking if it
worked or not each time, and if it didn't, was exiting
unhappily.
It seems to me that vol_id errors should probably be non-fatal, but I'm
not entirely sure what it's doing. In this instance I would still want
the appropriate scripts to be run for the device (to properly set up the
multipath stuff for the device) even if the device can't be read at the
moment.
Thanks,
Stephen
signature.asc
Description: Digital signature
