public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-ac5: dm-snapshot and XFS failures
Date: Fri, 5 Nov 2004 20:26:09 +0100	[thread overview]
Message-ID: <20041105192609.GA5843@sommrey.de> (raw)
In-Reply-To: <20041105073750.GA11812@sommrey.de>

On Fri, Nov 05, 2004 at 08:37:50AM +0100, Joerg Sommrey wrote:
> Hi,
> 
> in the last time I found some "strange" things happening while backing
> up.  For backing up I create a snapshot of all dm-devices, generate new
> UUIDs and mount the snapshot filesystems r/o (all XFS).
> While the backup was done there were hard lockups, XFS corruptions and
> a DM failure.

I was unable to remove the two stale snapshot volumes and tried to solve
that with a reboot.  "shutdown -r now" did hang. I was able to do a
SysRq-T trace, if this is of any interest. (rather large ~180K)

-jo

-- 
-rw-r--r--  1 jo users 63 2004-11-05 20:16 /home/jo/.signature

      reply	other threads:[~2004-11-05 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05  7:37 2.6.9-ac5: dm-snapshot and XFS failures Joerg Sommrey
2004-11-05 19:26 ` Joerg Sommrey [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=20041105192609.GA5843@sommrey.de \
    --to=jo@sommrey.de \
    --cc=linux-kernel@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