From: Wengang Wang <wen.gang.wang@oracle.com>
To: xfs@oss.sgi.com
Cc: greg.marsden@oracle.com, joe.jin@oracle.com
Subject: different error messages for mkfs.xfs -ssize
Date: Thu, 22 Apr 2010 23:36:36 +0800 [thread overview]
Message-ID: <20100422153636.GB3822@laptop.oracle.com> (raw)
Hi experts,
I got different error messages when provide different value for -ssize.
Why the error messages are different? They are different but no one is
containing more info than the other.
[root@desk test-xfsprogs]# mkfs.xfs -ssize=256 /dev/sda10 -f 2>&1 |head -n 1
illegal sector size 256
[root@desk test-xfsprogs]# mkfs.xfs -ssize=3072 /dev/sda10 -f 2>&1 |head -n 1
Illegal value 3072 for -s sectsize option
regards,
wengang.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-04-22 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:36 Wengang Wang [this message]
2010-04-22 16:18 ` different error messages for mkfs.xfs -ssize Kinzel, David
2010-04-23 2:48 ` Wengang Wang
2010-04-22 16:46 ` Christoph Hellwig
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=20100422153636.GB3822@laptop.oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=greg.marsden@oracle.com \
--cc=joe.jin@oracle.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