All of lore.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 10:17:04 +0200	[thread overview]
Message-ID: <44C33080.3060108@l4x.org> (raw)
In-Reply-To: <44C2EEC5.4020804@sandeen.net>

Eric Sandeen schrieb:
> Jan Dittmer wrote:
> 
>> Are there utilities for xfs which are able to ls and
>> cp from an _unmounted_ xfs volume? I fear that by
>> mounting the volume - even ro - I would lose even more
>> data.
>> Or can I achieve such an effect with other xfs related
>> utilities?
> 
> 
> Mounting ro should be fine - if you also mount with "norecovery" then 
> truly no IO should happen.  If you're really paranoid, find a utility to 
> mark the block device itself as read-only, then you've taken it out of 
> the filesystem's hands completely.

Thanks for the suggestions. Meanwhile I found the norecovery option
myself and got most of my data back. Strangely enough I had one top
directory missing on one mount attempt (only ro option) and it appeared
again on the next attempt (ro + norecovery).

> 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?

Thanks,

Jan

  reply	other threads:[~2006-07-23  9:26 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 [this message]
2006-07-23 14:21     ` Eric Sandeen
2006-07-23 15:34       ` Jan Dittmer

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=44C33080.3060108@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.