This is the mail archive of the
mailing list for the glibc project.
Re: Asking for Help on Seeking to End of File
- From: "Linda A. Walsh" <law at tlinx dot org>
- To: "Linlin Yan (颜林林)" <yanll at mail dot cbi dot pku dot edu dot cn>
- Cc: Ángel González <keisial at gmail dot com>, Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, Godmar Back <godmar at gmail dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Sat, 19 Jul 2014 20:15:46 -0700
- Subject: Re: Asking for Help on Seeking to End of File
- Authentication-results: sourceware.org; auth=none
- References: <CA+YjnUuUj_LeGTtGbuuOQy=YFR3HQ7ZHJ7h8XP1Y1ssEQA1Ryw at mail dot gmail dot com> <CAB4+JY+2Dhg1uo-+jputmfSjFtCMBFc7WQ1E3y1WXFYqZadiJQ at mail dot gmail dot com> <CA+YjnUs_CX4E14-JyrHXg8QeoL0YuaGpYFgRYVs7PJ3TCqN3cg at mail dot gmail dot com> <CAAHN_R0t8X7uN=J-JfLVZbt+_dB+uG0hybX2iq5VF_sZprV4bQ at mail dot gmail dot com> <5390EF18 dot 7010306 at gmail dot com> <CA+YjnUs7bfSaAUyvLJCd0mkx9mzpSq2X==BqB6K_7mpYYpO74g at mail dot gmail dot com> <CA+YjnUtbnkr6e4FSsBJ3DXhYkNPGOOaqquX9DipsX7csnQMfiA at mail dot gmail dot com>
Linlin Yan (éææ) wrote:
On Fri, Jun 6, 2014 at 8:18 AM, Linlin Yan (éææ)
root@ngs ~ # mount | grep '/rd'
/dev/mapper/rd on /rd type xfs
Thank you everyone!
I have finally found the problem. It is due to the mount parameter
"largeio" of the xfs file system. I tried to remove this parameter
before by running command "mount /dev/mapper/rd /rd -o remount", but
with no any effect. This time, I unmount the device and mount it again
without "largeio". It behaviours efficiently as expect now.
I know this is over a month past the post, but wanted to post a
to the above in case someone else stumbles upon this thread.
It's not the largeio, specifically that is causing the problem. By
it won't cause that behavior.
It's the allocsize
5.6. Mount Options - Large I/O
These mount options affect the preferred filesystem I/O size reported by
* A filesystem that has a swidth specified will return the swidth
value (in bytes) in st_blksize
* If the filesystem does not have a swidth specified but does
specify an allocsize then allocsize (in bytes) will be returned instead.
* The optimal I/O reported in st_blksize will be as small as
possible to allow user applications to avoid inefficient
If neither of these two options are specified, then the filesystem will
behave as if nolargeio was specified.
I.e. when the filesystem was mounted, someone specified that the file
system should try to make spaced for 1GB when it allocates space.
This would be great for files of 1GB in size, but not likely what you
want. I.e. largeio is designed to help xfs lay files out on disk
to prevent fragmentation by leaving space available for expansion
at the end of the file (controlled by the user on mount).
You might find out who or what was causing the file system to be
mounted with allocsize=1GB