[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#545179: libc6: postinst must run "telinit u"



On Mon, Sep 07, 2009 at 10:46:34AM +0200, Bastian Blank wrote:

> > I really can't explain you why the behaviour is still the same.
> 
> The mentioned bug shows a different problem.

I suspect that the referenced bug report was made with "/" being ext2,
while nowadays ext3 is the default. If I'm right, then the automatic
journal replay prevents fsck from complaining.

Hmm, I've found the logs of the first boot after the last libc upgrade:

dpkg.log fragment:

2009-08-31 21:36:58 status installed libc6 2.9-26

messages.log indicates the machine was shut down properly:

Aug 31 21:41:09 twister shutdown[20750]: shutting down for system halt
Aug 31 21:41:16 twister kernel: Kernel logging (proc) stopped.
Aug 31 21:41:16 twister kernel: Kernel log daemon terminating.
Aug 31 21:41:26 twister exiting on signal 15

kernel.log of the next boot:

Sep  1 07:11:31 twister kernel: [    4.286170] EXT3-fs: INFO: recovery required on readonly filesystem.
Sep  1 07:11:31 twister kernel: [    4.286272] EXT3-fs: write access will be enabled during recovery.
Sep  1 07:11:31 twister kernel: [    4.480816] kjournald starting.  Commit interval 5 seconds
Sep  1 07:11:31 twister kernel: [    4.480934] EXT3-fs: md0: orphan cleanup on readonly fs
Sep  1 07:11:31 twister kernel: [    4.481039] ext3_orphan_cleanup: deleting unreferenced inode 658
Sep  1 07:11:31 twister kernel: [    4.481076] ext3_orphan_cleanup: deleting unreferenced inode 529
Sep  1 07:11:31 twister kernel: [    4.490777] ext3_orphan_cleanup: deleting unreferenced inode 527
Sep  1 07:11:31 twister kernel: [    4.625170] EXT3-fs: md0: 3 orphan inodes deleted
Sep  1 07:11:31 twister kernel: [    4.625272] EXT3-fs: recovery complete.
Sep  1 07:11:31 twister kernel: [    4.628012] EXT3-fs: mounted filesystem with ordered data mode.
Sep  1 07:11:31 twister kernel: [    4.628130] VFS: Mounted root (ext3 filesystem) readonly on device 9:0.

So it's now the kernel that complains about the unclean shutdown
instead of fsck, but the issue seems to be very much the same.

Gabor

-- 
     ---------------------------------------------------------
     MTA SZTAKI Computer and Automation Research Institute
                Hungarian Academy of Sciences
     ---------------------------------------------------------



Reply to: