From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
ginermail@gmail.com
Subject: Re: [Bugme-new] [Bug 12112] New: Files with size more >2GB was truncated after copy by ncpfs
Date: Fri, 28 Nov 2008 21:59:53 -0800 [thread overview]
Message-ID: <4930DA59.7040205@vc.cvut.cz> (raw)
In-Reply-To: <20081127095436.4227d17f.akpm@linux-foundation.org>
Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Thu, 27 Nov 2008 09:12:29 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=12112
>>
>> Summary: Files with size more >2GB was truncated after copy by
>> ncpfs
>> Product: File System
>> Version: 2.5
>> KernelVersion: 2.6.27
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: high
>> Priority: P1
>> Component: Other
>> AssignedTo: fs_other@kernel-bugs.osdl.org
>> ReportedBy: ginermail@gmail.com
>>
>>
>> Latest working kernel version: none
>> Earliest failing kernel version: any
>> Distribution: Ubuntu/SuSE
>> Hardware Environment: any
>> Software Environment: any
>> Problem Description: I can't copy files more then 2Gb by ncpfs. They are
>> trancate.
>>
>> Steps to reproduce: Copy files from Netware/SuSE server to Ubuntu/SuSE desktop
>> by ncpfs.
ncpfs does not support files bigger than 4GB. If you get truncated
files, I guess that your app is at fault, it should get SIGXFSZ or an
error when you go over 4GB boundary:
(from fs/ncpfs/inode.c)
sb->s_flags |= MS_NODIRATIME; /* probably even noatime */
sb->s_maxbytes = 0xFFFFFFFFU;
sb->s_blocksize = 1024; /* Eh... Is this correct? */
Petr
prev parent reply other threads:[~2008-11-29 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12112-10286@http.bugzilla.kernel.org/>
2008-11-27 17:54 ` [Bugme-new] [Bug 12112] New: Files with size more >2GB was truncated after copy by ncpfs Andrew Morton
2008-11-29 5:59 ` Petr Vandrovec [this message]
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=4930DA59.7040205@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=ginermail@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.