Read/write counts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



    I have a file system that has really odd blocking.

    All files have a variable length header (basically a directory
entry) at their start.
    Most but not all sectors, have a small fixed length signature as
well as some link data at their start.

    The net result is that implimentation would be simpler if I could
just read/write, the amount of data
    that can be done with the least amount of work, even if that is less
than was requested.

    If I receive a request to read 512 bytes, and I return that I have
read 486, is either the OS, libc, or something else
    going to treat that as an error, or are they coming back for the
rest in a subsequent call ?

    I though I recalled that read()/write() returning a cound less than
requested is not an error.
   
   
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux