public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Schulze <schulze@informatik.uni-tuebingen.de>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump on mounted filesystem
Date: Fri, 29 May 2009 10:43:05 -0400	[thread overview]
Message-ID: <20090529144305.GA4882@infradead.org> (raw)
In-Reply-To: <8418003.3381243601790069.JavaMail.root@zcs-bi.informatik.uni-tuebingen.de>

On Fri, May 29, 2009 at 02:56:30PM +0200, Jan Schulze wrote:
> Hi all,
> 
> is it advisable to use xfsdump on a mounted file system, or am I likely to be running into problems when doing so? 

In fact xfsdump requires a mounted filesystem.

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

      reply	other threads:[~2009-05-29 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8097683.3361243601669032.JavaMail.root@zcs-bi.informatik.uni-tuebingen.de>
2009-05-29 12:56 ` xfsdump on mounted filesystem Jan Schulze
2009-05-29 14:43   ` 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=20090529144305.GA4882@infradead.org \
    --to=hch@infradead.org \
    --cc=schulze@informatik.uni-tuebingen.de \
    --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