public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Userspace cp and ls utility
Date: Sun, 23 Jul 2006 17:34:19 +0200	[thread overview]
Message-ID: <44C396FB.7050308@l4x.org> (raw)
In-Reply-To: <44C385DE.100@sandeen.net>

Eric Sandeen schrieb:
> Jan Dittmer wrote:
> 
>>> You could also try xfs_copy, it makes a copy of the filesystem and 
>>> works on the underlying device, with the filesystem unmounted.  
>>> There's a man page for it.
>>
>>
>> Is there any difference to using dd when the destination is no xfs
>> filesystem? And if I read the description correctly it does not allow
>> to copy individual files?
> 
> 
> xfs_copy knows about the xfs format, so it only copies what it needs 
> to.  dd will copy every bit on the source disk.  So, xfs_copy is more 
> efficient.  There is no option to copy individual files.
> 
> Depending on the problem with your original filesystem, perhaps xfs_copy 
> might not be the best choice.

Well I suffered from the 2.6.17 endian bug and had fun with dis- and re-
appearing folders upon xfs_repair and mount runs.
After all the 'only' thing I lost from my 600+gb volume are one or two
mailing list folders and most of my inbox (for which I've backups).
Seems to only affect folders which were open at the wrong moment.

Now I reformated the whole volume and restore the data from other
disks.

Jan

      reply	other threads:[~2006-07-23 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 10:48 Userspace cp and ls utility Jan Dittmer
2006-07-23  3:36 ` Eric Sandeen
2006-07-23  8:17   ` Jan Dittmer
2006-07-23 14:21     ` Eric Sandeen
2006-07-23 15:34       ` Jan Dittmer [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=44C396FB.7050308@l4x.org \
    --to=jdi@l4x.org \
    --cc=sandeen@sandeen.net \
    --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