From: "David H. Lynch Jr." <dhlii@comcast.net>
To: linux-fsdevel@vger.kernel.org
Subject: Read/write counts
Date: Mon, 04 Jun 2007 06:20:42 -0400 [thread overview]
Message-ID: <4663E77A.9040802@comcast.net> (raw)
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.
next reply other threads:[~2007-06-04 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 10:20 David H. Lynch Jr. [this message]
2007-06-04 16:33 ` Read/write counts Andreas Dilger
2007-06-04 16:56 ` Bryan Henderson
2007-06-04 17:02 ` Matthew Wilcox
2007-06-04 18:33 ` Theodore Tso
2007-06-04 18:57 ` Roman Zippel
2007-06-04 19:24 ` Joel Becker
2007-06-04 20:00 ` Theodore Tso
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=4663E77A.9040802@comcast.net \
--to=dhlii@comcast.net \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).