From: Emmanuel Florac <eflorac@intellique.com>
To: Tom Mason <tom_mason@me.com>
Cc: Brian Foster <bfoster@redhat.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Mount: Structure needs cleaning
Date: Tue, 14 Oct 2014 18:38:04 +0200 [thread overview]
Message-ID: <20141014183804.2baa8dd5@harpe.intellique.com> (raw)
In-Reply-To: <7630F174-D8AF-412D-8BBA-C3B1F7E05B9F@me.com>
Le Tue, 14 Oct 2014 16:46:39 +0100
Tom Mason <tom_mason@me.com> écrivait:
> > To copy the disk on another one, you can use ddrescue or dd with
> > "noerror" option.
> > -----------------------------------------
> Thanks again!
> Can I create an image on a new NAS drive such as a seagate 3tb
> 'Central network attached storage NAS' STCG3000200 without
> interfering with its capabilities as a NAS drive?
Yes of course, simply make a file image on the shared volume :
dd if=/dev/sdb2 noerror of=/mountpoint/mynas/disk1TB.img
Then you can run xfs_repair on the image file:
xfs_repair -f /mountpoint/mynas/disk1TB.img
Or run photorec on it
photorec /mountpoint/mynas/disk1TB.img
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-14 16:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 20:33 Mount: Structure needs cleaning Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25 ` Tom Mason
2014-10-13 23:44 ` Dave Chinner
2014-10-13 22:38 ` Tom Mason
2014-10-13 23:47 ` Dave Chinner
2014-10-14 10:55 ` Emmanuel Florac
2014-10-14 15:46 ` Tom Mason
2014-10-14 16:38 ` Emmanuel Florac [this message]
2014-10-14 16:43 ` Tom Mason
2014-10-21 20:44 ` Tom Mason
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 8:43 tommason
2014-10-12 14:20 ` Brian Foster
2014-10-12 22:39 ` tom mason
2014-10-12 22:48 ` tom mason
2014-10-12 22:51 ` tom mason
2014-10-12 23:10 ` Dave Chinner
2014-10-13 10:05 ` Tom Mason
2014-10-13 10:19 ` Emmanuel Florac
2014-10-13 10:40 ` Tom Mason
2014-10-13 9:26 ` Emmanuel Florac
2012-02-26 3:15 mount: " MikeJeezy
2012-02-26 4:35 ` Stan Hoeppner
2012-02-26 7:22 ` MikeJeezy
2012-02-26 17:07 ` Stan Hoeppner
2012-02-27 0:49 ` Dave Chinner
2012-02-27 3:11 ` MikeJeezy
2012-02-27 6:28 ` Stan Hoeppner
2012-02-27 18:32 ` MikeJeezy
2012-02-28 1:48 ` Dave Chinner
2012-02-28 9:14 ` Brian Candler
2012-02-29 3:50 ` Dave Chinner
2012-02-29 7:40 ` Brian Candler
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=20141014183804.2baa8dd5@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=bfoster@redhat.com \
--cc=tom_mason@me.com \
--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