public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Guido Doornberg" <guidodoornberg@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] fsck seems to screw up my harddisk
Date: Fri, 12 Jan 2007 16:38:21 +0100	[thread overview]
Message-ID: <eb2db630701120738u56f0c240n13a6939e17b237cb@mail.gmail.com> (raw)
In-Reply-To: <200612042153.42774.bss03@volumehost.net>

So, here I am again,

now without the samsung drive, but this time (same system), with a
software RAID-1, on 2 Western Digital Caviar Disks, working with ext2
on the boot-, and reiserfs on the rootpartition.

Anyway, every time the system shuts down, the last things my pc tells me are:

* Unmounting filesystems ...						[ ok ]
* Shutting down RAID devices (mdadm) ...
md: md1 stopped.
md: unbind<sdb1>
md: export_rdev(sdb1)
md: unbind<sda1>
md: export_rdev(sda1)
md: md2 stopped.
md: unbind<sdb2>
md: export_rdev(sdb2)
md: unbind<sda2>
md: export_rdev(sda2)
md: md3 still in use.
md: md3 still in use.
md: md3 still in use.
mdadm: stopped /dev/md1
mdadm: stopped /dev/md2
mdadm: fail to stop array /dev/md3: Device or resource busy		[ !! ]
* Remounting remaining filesystems readonly ...				[ ok ]
md: stopping all md devices.
md: md3 still in use.
Synchronizing SCSI cache for disk sdb:
Synchronizing SCSI cache for disk sda:
System halted.

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?

btw, if you think I should post this kind of questions somewhere else,
I'd be happy to hear so...

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



  reply	other threads:[~2007-01-12 15:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 18:16 [gentoo-amd64] fsck seems to screw up my harddisk Guido Doornberg
2006-11-27 18:44 ` Richard Fish
2006-11-27 19:08   ` Alexander Gabert
2006-11-27 22:42     ` Richard Freeman
2006-11-27 19:32   ` Guido Doornberg
2006-11-27 20:03     ` Bernhard Auzinger
2006-11-28  1:49     ` Richard Fish
2006-12-03 13:40       ` Guido Doornberg
2006-12-03 17:04         ` [gentoo-amd64] " Duncan
2006-12-03 17:54           ` Drake Donahue
2006-12-04 10:16       ` [gentoo-amd64] " Peter Humphrey
2006-12-04 11:31         ` Jesús Guerrero
2006-12-04 11:35         ` [gentoo-amd64] " Duncan
2006-12-05  3:53         ` [gentoo-amd64] " Boyd Stephen Smith Jr.
2007-01-12 15:38           ` Guido Doornberg [this message]
2007-01-12 17:30             ` Adam James
2007-01-12 18:26               ` Guido Doornberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb2db630701120738u56f0c240n13a6939e17b237cb@mail.gmail.com \
    --to=guidodoornberg@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox