| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | XFS setting custom extent size: real-time section only? |
| From: | Heilige Gheist <hgheist@xxxxxxxxx> |
| Date: | Sun, 23 Jul 2006 04:09:18 -0700 (PDT) |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=sUBOZXobGsjjyIt2o8LinmyHSUeLB0ApL/fyce9UckDwdK1ADzH5yKP4u8tE6wAdP1o7gPnmVKbByDKOC9EJo1L6uHfT+0m1iDIEckNTxNMnBv7ryTMte0qGyH+j0QZW+HQMiHDJPPC0Cf+VZ4JChGxJYAaZGpvcnTyZW9DDqb0= ; |
| Sender: | xfs-bounce@xxxxxxxxxxx |
I'm trying to get custom extent size per file working, but XFS_IOC_FSSETXATTR ioctl returns with EINVAL, both from my code or from xfs_io. The environment is SLES9 SP2, 2.6.5-7.252 kernel, xfsprogs-2.6.25-0.6 After examining the kernel code in xfs_vnodeops.c we found out that custom extent size is supported on files in real-time section only. This is not mentioned anywhere else in the documentation, so I'm wondering whether this limitation is removed in further kernel versions. I've downloaded the recent xfsprogs-2.8.4, it uses a new flag XFS_XFLAG_EXTSIZE when setting the custom extent size. I'm not sure what kernel version do I need to work with 2.8.4, but it's certainly a sign that kernel support has changed. Can anyone shed a light on this? Thanks, Alan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Userspace cp and ls utility, Jan Dittmer |
|---|---|
| Next by Date: | Re: Userspace cp and ls utility, Eric Sandeen |
| Previous by Thread: | Page allocation failure writing to an XFS volume via NFS on CentOS 4.3, Luca Maranzano |
| Next by Thread: | Re: XFS setting custom extent size: real-time section only?, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |