Re: [gentoo-amd64] fsck seems to screw up my harddisk

[Adam James <atj@pulsewidth.org.uk>]

On Fri, 12 Jan 2007 16:38:21 +0100 "Guido Doornberg"
<guidodoornberg@gmail.com> wrote:

> So, my question is quite simple i guess; Is it normal that my array
> (/dev/md3) doesn't like to be stopped? And if it isn't, how can I make
> it stop?

It would be helpful if you told us what filesystems you have mounted
on '/dev/md3'.

If it is your root partition, then it makes sense that it cannot be
unmounted, as the programs and files used in the shutdown are located
on it! This is not a problem however, as part of the shutdown process is
to remount as read-only any filesystems that cannot be cleanly
unmounted.

> * Remounting remaining filesystems readonly ...				[ ok ]

This prevents any further writes to the disk, while still allowing
processes access to their data.

> Synchronizing SCSI cache for disk sdb:
> Synchronizing SCSI cache for disk sda:

Disk buffers are then synchronised to disk, removing any risk of data
corruption, and the system is halted.

> System halted.

So in answer to your question, it is quite normal and is not a problem.
If '/dev/md3' does not house your root partition, then it probably
contains a daemon that is refusing to shutdown in an orderly
manner. Running `lsof /partition` might help you track it down.

-atj
-- 
gentoo-amd64@gentoo.org mailing list