From: Nathan Scott <nscott@aconex.com>
To: wkendall@sgi.com
Cc: xfs@oss.sgi.com
Subject: xfsdump buglets
Date: Fri, 16 Mar 2007 14:25:36 +1100 [thread overview]
Message-ID: <1174015536.5051.193.camel@edge> (raw)
Hey Bill,
Got a couple of minor xfsdump problems reported to me, they're probably
straightforward for someone who knows xfsdump well - here ya go...
cheers.
-------- Forwarded Message --------
From: Peter Chubb <peterc@gelato.unsw.edu.au>
Reply-To: Peter Chubb <peterc@gelato.unsw.edu.au>,
415080@bugs.debian.org
To: submit@bugs.debian.org
Subject: Bug#415080: Poor error message from xfsdump for incorrect args
Date: Fri, 16 Mar 2007 09:47:50 +1100
Package: xfsdump
Version: 2.2.38-1
I do:
xfsdump -l 0 -p -f afile filesystem
and get
xfsdump: ERROR: -^@ argument missing
because -p needs a numeric argument.
The message should say -p argument missing.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
------- Forwarded Message --------
From: Peter Chubb <peterc@gelato.unsw.edu.au>
Reply-To: Peter Chubb <peterc@gelato.unsw.edu.au>,
415081@bugs.debian.org
To: submit@bugs.debian.org
Subject: Bug#415081: xfsdump doesn't accept relative pathnames to
mountpoints
Date: Fri, 16 Mar 2007 09:54:52 +1100
Package: xfsdump
Version: 2.2.38-1
I have a filesystem mounted at /export.
I do:
cd /
xfsdump -l 0 -f /path/to/file export
and see
xfsdump: ERROR: export does not identify a file system
xfsdump -l 0 -f /path/to/file /export
works.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
--
Nathan
next reply other threads:[~2007-03-16 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 3:25 Nathan Scott [this message]
2007-03-16 4:42 ` xfsdump buglets Kouta Ooizumi
2007-03-16 5:05 ` Nathan Scott
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=1174015536.5051.193.camel@edge \
--to=nscott@aconex.com \
--cc=wkendall@sgi.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