public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: "linux-xfs@oss.sgi.com" <linux-xfs@oss.sgi.com>
Subject: Re: XFS Journal on md device
Date: Wed, 6 Sep 2006 06:12:45 +0200	[thread overview]
Message-ID: <20060906041245.GA10066@piper.madduck.net> (raw)
In-Reply-To: <2260b150609052053h31731a0eycababfab603749c9@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

also sprach Chris Seufert <seufert@gmail.com> [2006.09.06.0553 +0200]:
> My root (/) volume is ext3 running on /dev/md0 (RAID 1), the
> problem is with my /data volume thats xfs, running on /dev/sda,
> with log on /dev/md4.

Can you tell when /data gets umounted during the shutdown sequence?
Correct me if I'm wrong, but once that happened, /dev/md4 should
become free as far as XFS is concerned.

However, since mdadm or the kernel fails to stop the device during
shutdown, I am guessing that the partition is simply not being
umounted.

Does it have an entry in /etc/fstab?

Try changing the 

  #! /bin/sh

in line 1 of /etc/rc6.d/S40umountfs to

  #! /bin/sh -x
  exec 2> /root/umountfs.out.2

then reboot and paste that file somewhere (http://rafb.net/paste).

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
spamtraps: madduck.bogus@madduck.net
 
"you don't sew with a fork, so I see no reason
 to eat with knitting needles."
                               -- miss piggy, on eating chinese food

[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-09-06  5:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 23:40 XFS Journal on md device Chris Seufert
     [not found] ` <44FE28A8.5000803@oss.sgi.com>
2006-09-06  1:53   ` Chris Seufert
2006-09-06  1:55     ` Chris Seufert
2006-09-06  3:40     ` martin f krafft
2006-09-06  3:53       ` Chris Seufert
2006-09-06  4:12         ` martin f krafft [this message]

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=20060906041245.GA10066@piper.madduck.net \
    --to=madduck@madduck.net \
    --cc=linux-xfs@oss.sgi.com \
    /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