On Feb 25, 2007 21:11 -0500, Oleg Drokin wrote: > > And what about workaround for the moment ? What is the solution at short > > term ? > > Do not use streaming i/o functions for now? > It's also possible to decrease st_blksize reported by lustre by patching > lustre.
With older versions of Lustre if you specified a striping like 65536 bytes then st_blksize would be returned with stripes * stripe_size. This caused problems with NFS export and connectathon because NFS creates files via mknod() and they don't have file striping associated until the file is opened, so the st_blksize could change on a file. We might want to consider revisiting this change. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
