From: David Chow <davidchow@shaolinmicro.com>
To: linux-fsdevel@vger.kernel.org
Subject: LFS/non-LFS error handling
Date: Sat, 13 Apr 2002 00:46:14 +0800 [thread overview]
Message-ID: <3CB70F56.8030004@shaolinmicro.com> (raw)
Dear all,
If my fs don't support LFS (files larger than 4GB), what should I set in
my sb->s_maxbytes? In kernel 2.4.2 , I have experieced if not set the
s_maxbytes generic_file_write() will fail, but for later version of
kernel I simply leave it unset, so far I don't have any problem. If it
is wrong, what should s_maxbytes=? . Since this behaviour changes across
kernel version, is there a standard implemenation?
Since it still work for me for not setting the s_maxbytes, it seems to
me there is a potential risk of data corruption at limit points, because
don't know who to handle the over flow situation, does this handle by
VFS? or I have to take care myself? Thanks.
regards,
David
next reply other threads:[~2002-04-12 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 16:46 David Chow [this message]
2002-04-12 23:18 ` LFS/non-LFS error handling Ion Badulescu
2002-04-13 16:38 ` David Chow
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=3CB70F56.8030004@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--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