From: Stan Hoeppner <stan@hardwarefreak.com>
To: lord worm <cryptopsy@live.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs Digest, Vol 29, Issue 102
Date: Mon, 31 Jan 2011 12:31:12 -0600 [thread overview]
Message-ID: <4D46FFF0.5090405@hardwarefreak.com> (raw)
In-Reply-To: <SNT130-w323D725C89EB3F13E94A3BDAE20@phx.gbl>
lord worm put forth on 1/30/2011 10:41 PM:
> Stan, do you check dates on links before you paste them here? I don't care if its the 1st results of the google search 'meaning of life', its irrelevant and oudated.
At the time I sent that reply, you had posted no log information, nothing
concrete to allow us to focus our troubleshooting efforts. At that time, the
information in the link I provided could have been as relevant as any other. At
that time I had not seen the off list back-n-forth between you and Dave that
contained a little bit more information from you. Note that I said "might be
relevant", not "this is your answer".
Note that Dave recently pointed an OP to a 1996 XFS paper. Some information in
that 15 year old paper is still relevant today. You cannot simply discard
information because it appears "old" to you. Some aspects of XFS haven't
changed in 16 years.
As I said in my first response, xfsdump/xfsrestore would have avoided your
current problem, as well as xfs_copy, as Dave pointed out.
There is nothing set in stone that prevents dd from working with XFS
filesystems. However, it is obviously less forgiving of error, user or
otherwise, than the 'equivalent' XFS utilities.
Lastly, getting testy with those attempting to assist you isn't going to further
your efforts in fixing your problem.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-01-31 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1364.1296445754.4020.xfs@oss.sgi.com>
2011-01-31 4:41 ` xfs Digest, Vol 29, Issue 102 lord worm
2011-01-31 18:31 ` Stan Hoeppner [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=4D46FFF0.5090405@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=cryptopsy@live.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