From: Rene Salmon <rsalmon@tulane.edu>
To: xfs@oss.sgi.com
Cc: Rene Salmon <rsalmon@tulane.edu>
Subject: LVM and XFS cannot set blocksize on block device
Date: Mon, 25 Sep 2006 17:11:48 -0500 [thread overview]
Message-ID: <45185424.2030707@tulane.edu> (raw)
Hi,
I am trying to create an xfs file system on and LVM logical volume.
the actual physical drive has blocks or sectors of 4096.
when I try to make the xfs file system on top of LVM I get this message:
helix-priv:~ # mkfs.xfs -f /dev/vg_u00/lv_u00
mkfs.xfs: warning - cannot set blocksize on block device
/dev/vg_u00/lv_u00: Invalid argument
Warning: the data subvolume sector size 512 is less than the sector size
reported by the device (4096).
meta-data=/dev/vg_u00/lv_u00 isize=256 agcount=32,
agsize=11489280 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=367656960, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
helix-priv:~ #
any ideas?
Thanks
Rene
--
-
--
Rene Salmon
Tulane University
Center for Computational Science
http://www.ccs.tulane.edu
rsalmon@tulane.edu
Tel 504-862-8393
Tel 504-988-8552
Fax 504-862-8392
next reply other threads:[~2006-09-25 23:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 22:11 Rene Salmon [this message]
2006-09-26 0:17 ` LVM and XFS cannot set blocksize on block device Chris Wedgwood
2006-09-26 13:58 ` Rene Salmon
2006-09-26 22:40 ` Chris Wedgwood
2006-09-27 11:55 ` Shailendra Tripathi
2006-09-27 13:16 ` Rene Salmon
2006-09-28 10:33 ` Tim Shimmin
2006-09-27 15:48 ` Eric Sandeen
2006-09-28 10:23 ` Tim Shimmin
2006-09-28 15:32 ` Chris Wedgwood
2006-10-02 7:28 ` Timothy Shimmin
2006-10-03 7:35 ` Timothy Shimmin
2006-10-06 20:36 ` Rene Salmon
2006-10-11 9:59 ` Timothy Shimmin
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=45185424.2030707@tulane.edu \
--to=rsalmon@tulane.edu \
--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.