Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: How to force stopping an array`
Date: Tue, 27 May 2008 15:42:51 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0805271542240.19633@p34.internal.lan> (raw)
In-Reply-To: <200805271249.35965.Dexter.Filmore@gmx.de>



On Tue, 27 May 2008, Dexter Filmore wrote:

> Am Dienstag, 27. Mai 2008 02:05:36 schrieb NeilBrown:
>> On Tue, May 27, 2008 9:02 am, Dexter Filmore wrote:
>>> Am Dienstag, 27. Mai 2008 00:30:26 schrieb Justin Piszcz:
>>>> On Tue, 27 May 2008, Dexter Filmore wrote:
>>>>> Am Dienstag, 27. Mai 2008 00:06:57 schrieb Justin Piszcz:
>>>>>> On Mon, 26 May 2008, Dexter Filmore wrote:
>>>>>>> So I have a filesystem on an array I cannot unmount, hence I cannot
>>>>>>> stop the array.
>>>>>>> Any way to force it?
>>>>>>>
>>>>>>> Dex
>>>>>>
>>>>>> What is using it?
>>>>>>
>>>>>> lsof | grep /mount_point
>>>>>> lsof | grep /dev/mdX
>>>>>
>>>>> A defunct java process that died from a mem heap error. I can't kill
>>>>
>>>> the
>>>>
>>>>> process, not even -9, leaves a <defunct>.
>>>>
>>>> Other than rebooting I am not sure..  You could try making / re-mounting
>>>> it as read-only but if the java process is still reading from the FS it
>>>> probably will not be of any help.
>>>>
>>>> Justin.
>>>
>>> Exactly. reboot pretty much deosn't do any good, afterwars the raid
>>> resyncs,
>>> which takes full 7h here.
>>
>> There shouldn't be a resync.  Presumably nothing is writing to the
>> array, and moments after the last write, the array will have been
>> flagged as 'clean' and will not require a resync after a reboot.
                                              ^^^^^^^^^^^^^^^^^^^^^^

His host crashed != reboot so that is the reason for the resync.

>
> Well, that's what I thought. Actually the "shutdown" didn't work at all, it
> got stuck and wouldn't finish so I had to resort to Alt-SysRq-S/U/B to
> reboot.
> S/U should have ensured the file systems are in sync, but I don't know how the
> array takes to such measures. After the reboot the mdstat looks...
>>
>>> What happens there anyway? it resyncs, but mdstats say [UUUUU], all fine.
>>
>> I don't understand this question.
>>
>
> ...like this:
>
> # cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : active raid5 sde1[0] sdb1[4] sdd1[3] sda1[2] sdc1[1]
>      1953503488 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
>      [>....................]  resync =  2.9% (14600832/488375872)
> finish=360.6min speed=21896K/sec
>
> unused devices: <none>
>

Justin.


  reply	other threads:[~2008-05-27 19:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 21:43 How to force stopping an array` Dexter Filmore
2008-05-26 22:06 ` Justin Piszcz
2008-05-26 22:26   ` Dexter Filmore
2008-05-26 22:30     ` Justin Piszcz
2008-05-26 23:02       ` Dexter Filmore
2008-05-27  0:05         ` NeilBrown
2008-05-27 10:49           ` Dexter Filmore
2008-05-27 19:42             ` Justin Piszcz [this message]
2008-05-30  1:54               ` Neil Brown
2008-05-30 11:18                 ` Dexter Filmore

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=alpine.DEB.1.10.0805271542240.19633@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=Dexter.Filmore@gmx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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