public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stuart Rowan <strr-debian@decisionsoft.co.uk>
Cc: xfs@oss.sgi.com
Subject: Re: Oops during umount of r/o file system
Date: Sun, 15 Feb 2009 14:18:16 -0500	[thread overview]
Message-ID: <20090215191816.GA4626@infradead.org> (raw)
In-Reply-To: <499540B1.2080100@decisionsoft.co.uk>

On Fri, Feb 13, 2009 at 09:43:13AM +0000, Stuart Rowan wrote:
> I fetched and installed the linux-image-2.6.26-bpo.1-amd64 package from  
> backports.org.
>
> This is the Debian lenny kernel, but backported to etch. It looks to be  
> 2.6.26.8 and a few patches. I realise the "and a few patches" sounds bad  
> but usually with Debian they are minor things like adding device ids.
>
> uname -a:
> Linux tigris 2.6.26-bpo.1-amd64 #1 SMP Wed Dec 17 12:18:36 UTC 2008  
> x86_64 GNU/Linux
>
> We do the following as part of our backup script:
>
> mkdir -p /tmp/dev/data/home-xfs; /usr/sbin/xfs_freeze -f /home ;  
> /sbin/lvcreate -s -L 20G -n snap-shot /dev/data/home-xfs ;  
> /usr/sbin/xfs_freeze -u /home && mount -o nouuid,ro /dev/data/snap-shot  
> /tmp/dev/data/home-xfs
>
> (rsync the snapshot offsite)
>
> umount /tmp/dev/data/home-xfs ; /sbin/lvremove -f /dev/data/snap-shot
>
> The umount, intermittently, of this ro filesystem hangs until a reboot  
> as below.

Any chance you could capture the output of dmesg after an

	echo t > /proc/sysrq-trigger

to see where it hangs exactly?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-02-15 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13  9:43 Oops during umount of r/o file system Stuart Rowan
2009-02-15 19:18 ` Christoph Hellwig [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=20090215191816.GA4626@infradead.org \
    --to=hch@infradead.org \
    --cc=strr-debian@decisionsoft.co.uk \
    --cc=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