From: "NeilBrown" <neilb@suse.de>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-raid@vger.kernel.org
Subject: Re: How to force stopping an array`
Date: Tue, 27 May 2008 10:05:36 +1000 (EST) [thread overview]
Message-ID: <40275.192.168.1.70.1211846736.squirrel@neil.brown.name> (raw)
In-Reply-To: <200805270102.15029.Dexter.Filmore@gmx.de>
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.
> What happens there anyway? it resyncs, but mdstats say [UUUUU], all fine.
I don't understand this question.
NeilBrown
next prev parent reply other threads:[~2008-05-27 0:05 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 [this message]
2008-05-27 10:49 ` Dexter Filmore
2008-05-27 19:42 ` Justin Piszcz
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=40275.192.168.1.70.1211846736.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=Dexter.Filmore@gmx.de \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.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