From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: [REVIEW 2/2] Case insensitive support for XFS - user-space
Date: Fri, 18 Jan 2008 15:23:27 -0600 [thread overview]
Message-ID: <479118CF.1020302@sandeen.net> (raw)
In-Reply-To: <op.t43zfeiz3jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> This patch relies on the dinode.c refactoring patch posted recently.
> I have attached the latest version (with fixes pointed out by Chandan).
So, new mkfs.xfs -h output says:
/* naming */ [-n log=n|size=num,version=n,utf8=none|default|turkic]
so I tried:
mkfs.xfs -dfile,name=fsfile,size=500m -nutf8=none
and got:
Illegal value none for -n utf8 option
(are there man page updates lurking somewhere? Pls also update
Documentation/filesystems/xfs.txt in the kernel)
....
Also, if I specify -nutf8=default on a 500m fs:
# mkfs.xfs -dfile,name=fsfile,size=500m -nutf8=default
meta-data=fsfile isize=256 agcount=4, agsize=32000 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=128000, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 utf8=default
log =internal log bsize=4096 blocks=1200, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: cannot reserve space: No space left on device
However this works:
# mkfs.xfs -dfile,name=fsfile,size=500m
as does this:
# mkfs.xfs -dfile,name=fsfile,size=1000m -nutf8=default
eh? :)
-Eric
next prev parent reply other threads:[~2008-01-18 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 4:43 [REVIEW 2/2] Case insensitive support for XFS - user-space Barry Naujok
2008-01-18 21:23 ` Eric Sandeen [this message]
2008-01-19 6:00 ` Eric Sandeen
2008-01-21 2:07 ` Barry Naujok
2008-01-21 2:16 ` Barry Naujok
2008-01-21 2:31 ` Eric Sandeen
2008-01-21 0:54 ` Barry Naujok
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=479118CF.1020302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=xfs-dev@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 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.