linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bug 54551] New: write fails with one short >2GB write.
@ 2013-02-27 14:49 bugzilla-daemon
  2013-02-27 14:51 ` [Bug 54551] " bugzilla-daemon
  2013-03-01  9:20 ` bugzilla-daemon
  0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2013-02-27 14:49 UTC (permalink / raw)
  To: linux-ext4

https://bugzilla.kernel.org/show_bug.cgi?id=54551

           Summary: write fails with one short >2GB write.
           Product: File System
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: meetmehiro@gmail.com
        Regression: No


Hi,

I have one application where we are writing on-short 3G of data but when write
succeed, it writes only 2G of data.

simple program.

if ( (ret = write(fd,buf,3221225472)) != limit) {

printf("\nError no:=%d",errno);
printf("\nret : %d",ret);
}

in above program, write only writes 2GB data..

could you please tell me, how to resolve this..

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 54551] write fails with one short >2GB write.
  2013-02-27 14:49 [Bug 54551] New: write fails with one short >2GB write bugzilla-daemon
@ 2013-02-27 14:51 ` bugzilla-daemon
  2013-03-01  9:20 ` bugzilla-daemon
  1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2013-02-27 14:51 UTC (permalink / raw)
  To: linux-ext4

https://bugzilla.kernel.org/show_bug.cgi?id=54551





--- Comment #1 from meetmehiro@gmail.com  2013-02-27 14:51:38 ---
is it like, "MAX_RW_COUNT" limit is 2G ?????

is there any way, we can bypass this limit, pls help me out into this..

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 54551] write fails with one short >2GB write.
  2013-02-27 14:49 [Bug 54551] New: write fails with one short >2GB write bugzilla-daemon
  2013-02-27 14:51 ` [Bug 54551] " bugzilla-daemon
@ 2013-03-01  9:20 ` bugzilla-daemon
  1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2013-03-01  9:20 UTC (permalink / raw)
  To: linux-ext4

https://bugzilla.kernel.org/show_bug.cgi?id=54551


Jan Kara <jack@suse.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@suse.cz
         AssignedTo|fs_ext4@kernel-bugs.osdl.or |jack@suse.cz
                   |g                           |




--- Comment #2 from Jan Kara <jack@suse.cz>  2013-03-01 09:20:51 ---
You cannot easily overcome this limit. Also I'd note that POSIX does not say
how much is going to be written. So you have to be prepared for the fact that
your write writes e.g. 1 byte (although in practice that doesn't tend to
happen). If some program relies on write(2) writing as much as it was told to,
it is a buggy program.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-03-01  9:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-27 14:49 [Bug 54551] New: write fails with one short >2GB write bugzilla-daemon
2013-02-27 14:51 ` [Bug 54551] " bugzilla-daemon
2013-03-01  9:20 ` bugzilla-daemon

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).