From: "Barry Naujok" <bnaujok@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
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: Mon, 21 Jan 2008 13:16:17 +1100 [thread overview]
Message-ID: <op.t49clfbc3jf8g2@pc-bnaujok.melbourne.sgi.com> (raw)
In-Reply-To: <op.t49b6jkr3jf8g2@pc-bnaujok.melbourne.sgi.com>
On Mon, 21 Jan 2008 13:07:21 +1100, Barry Naujok <bnaujok@sgi.com> wrote:
> On Sat, 19 Jan 2008 17:00:52 +1100, Eric Sandeen <sandeen@sandeen.net>
> wrote:
>
>> Eric Sandeen wrote:
>>
>>> 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
>>
>> /*
>> * allocate the inode
>> */
>> tp = libxfs_trans_alloc(mp, 0);
>> error = libxfs_trans_reserve(tp, XFS_CREATE_LOG_RES(mp), 0, 0,
>> 0, 0);
>
> Can you try this instead?
>
> error = libxfs_trans_reserve(tp, XFS_IALLOC_BLOCKS(mp) +
> (XFS_IN_MAXLEVELS(mp) - 1), 0, 0, 0, 0);
BTW. this fix works for me :)
>> if (error) {
>> fprintf(stderr, _("%s: 1: cannot reserve space: %s
>> (%d)\n"),
>> progname, strerror(error),
>> XFS_CREATE_LOG_RES(mp));
>> exit(1);
>> }
>>
>>
>> I think there are some wrong arguments to that trans_reserve... at least
>> XFS_CREATE_LOG_RES should be 3rd arg, no?
>>
>> -Eric
>
>
>
>
next prev parent reply other threads:[~2008-01-21 2:15 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
2008-01-19 6:00 ` Eric Sandeen
2008-01-21 2:07 ` Barry Naujok
2008-01-21 2:16 ` Barry Naujok [this message]
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=op.t49clfbc3jf8g2@pc-bnaujok.melbourne.sgi.com \
--to=bnaujok@sgi.com \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox