similar to: [Bug 1195] sftp corrupts large files on new macbook pro

Hi, I tried to compile rsync-2.5.2 on Solaris 5.7 Ultra-2 machine, 5.7 on Ultra-2 is running 64 bit, but, when I ran configure, it said no for largefile, I thought 2.5.2 will support large file? Is that true? Thanks, Jennifer

I'm attempting to decode part of a largefile flac whose seektable is broken or missing and the file is shorter then it's supposed to be, when I use 1.1.2 it decodes fine, when I use 1.1.3 it fails flac --decode --skip=719:58.0 --until=1024:58.0 -o \/home\/sbh\/work\/hs\/out.wav \/mnt\/ss\/sdb\/Sound\/Recording\/2006\-11\-29\/in.flac out.wav: ERROR seeking while skipping bytes

I'm attempting to decode part of a largefile flac whose seektable is broken or missing and the file is shorter then it's supposed to be, when I use 1.1.2 it decodes fine, when I use 1.1.3 it fails flac --decode --skip=719:58.0 --until=1024:58.0 -o \/home\/sbh\/work\/hs\/out.wav \/mnt\/ss\/sdb\/Sound\/Recording\/2006\-11\-29\/in.flac out.wav: ERROR seeking while skipping bytes

I have downloaded the source for rsync 2.5.6 and compiled it without adjusting any options, no problems. Performed a test copy of a file GT 2 GB and it failed. In the file configure I changed the line to "--enable-largefile", removed all the .o files, performed a ./configure, gmake, gmake install. Tried the test copy and again received the following error message: rsync:

Hello,     Installing bind9 on my Ubuntu 14.04 via. apt-get displays the following options.  #named -V BIND 9.9.5-3ubuntu0.16-Ubuntu (Extended Support Version) <id:f9b8a50e> built by make with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads'

Hello , review bind9 options ... >> Dec 22 12:25:55 verdandi named[18534]: starting BIND 9.9.5-7-Debian -u >> bind -4 >> Dec 22 12:25:55 verdandi named[18534]: built with '--prefix=/usr' >> '--mandir=/usr/share/man' '--infodir=/usr/share/info' >> '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads'

Hi, I am running RH 7.2 (professional release 2.4 kernel) I have a ext3 file system which stores large oracle "dump files" over 4GB. We write to it via NFS which is working great, the problem is when we issue a file largefile.dmp from the linux box it fails on anything over 4GB stating that can't stat 'largefile.dmp' (value too large for defined data type). We can do

(2013/03/05 12:27), Cristian Rodr?guez wrote: > Nothing against you code, that's ugly ..but as it is a first step it can > be forgiven :-) > > I will just force flac to be built with 64 bit file offsets and just > reject any caller trying to include/link libflac into a non-lfs program > like > > http://ac-archive.sourceforge.net/largefile/off_t_headers.html > >

On 12/30/2015 4:14 PM, Rowland penny wrote: > ./configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --sysconfdir=/etc/bind --localstatedir=/var > --enable-threads --enable-largefile --with-libtool --enable-shared > --enable-static --with-openssl=/usr --with-gssapi=/usr > --with-dlopen=yes --with-gnu-ld --enable-ipv6 > CFLAGS='-fno-strict-aliasing

https://bugzilla.netfilter.org/show_bug.cgi?id=1195 Bug ID: 1195 Summary: 'list ruleset' of 'nft -f' outputs garbage while 'nft list ruleset' seems to work. Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement

Hello, I can't transfer big files. In the output below, you can see that rsync only transfer 1383275520 of a 5448046592 bytes file: F:\shells>rsync -e ssh -avz ./backup chris@myhost.com:backups chris@myhost.com's password: building file list ... done wrote 114 bytes read 20 bytes 3.01 bytes/sec total size is 1383275520 speedup is 10322951.64 I've tried with other big files and

Dear Rowland , Just keep in mind that the Debian RPI maintated by rasperry.org PI fellows and _not_ mainly by the Mainsteam debian pkg maintainers, and ways behind the main distro - allmost. > > Even though there is no mention of dlopen, samba_dlz works. > yes/no ->> its not displaying the DLZ file open <<- and that happen even on my now +1J old samba4.0 RPI samba4 ad.

I created a filesystem as follows: mke2fs -j -O dir_index -O sparse_super -T largefile /dev/drbd/6 Here's the the output from df Filesystem Size Used Avail Use% /dev/drbd/6 475G 33M 452G 1% It seems that ext3 has taken 23 GB, which is about 5% of the total disk size, for itself. Is that right? If that is, indeed, the case, why does df just list 33M as being

Hello, currently we're using version 1.0.13 with 32bit file offsets. Is it safe to switch to a new version with largefile support enabled ? We want to reuse existing index/cache or do we have to expect errors with that ? Regards. Martin --------------------------------------------------------------- Martin Preen, Universit?t Freiburg, Institut f?r Informatik Georges-Koehler-Allee 52, Raum

Hi, I want to use an ext3 Partition (~1TB) for Mail Storage, this means tons of small files. Has anyone recommendations about blocksize, inodes, etc. for mkfs.ext3 ? Thanks in advance, David -- View this message in context: http://www.nabble.com/Ext3----which-blocksize-for-small-files--tf2601442.html#a7257363 Sent from the Ext3 - User mailing list archive at Nabble.com.

Solaris in 32-bit mode has a 1TB device limit. UFS filesystems in 32-bit mode also have a 1TB limit, even if using a logical volume manager to span smaller than 1TB devices. So, what kind of limit does ZFS have when running under 32-bit Solaris? -- Erik Trimble Java System Support Mailstop: usca14-102 Phone: x17195 Santa Clara, CA

Hello, I investigated newsgroups and mailinglists for aprox. 3 weeks now. But i have not found any comment about ext3 freezing a whole system. But: I do have 5 ext2 partitions on my system. I upgraded theses partitions to ext3 with tunefs. after mounting 1 partition as ext3 all was fine. After that i mounted all partitions as ext3. And, after approx. 3-4 minutes my system freezes. No mouse or

On 12/11/06, Josh Coalson <xflac@yahoo.com> wrote: > --- Avuton Olrich <avuton@gmail.com> wrote: > > I'm attempting to decode part of a largefile flac whose seektable is > > broken or missing and the file is shorter then it's supposed to be, > > when I use 1.1.2 it decodes fine, when I use 1.1.3 it fails > > > > flac --decode --skip=719:58.0

Hi, I need to to open existing readonly files. Yes you are right, not the open call takes the time, but stat() system call. I looked at aio_pthread source, the lines which needs to be removed to make it work are just the lines which tests for O_CREAT|O_EXCL? What problems can cause such solution for readonly share? On Tue, Apr 26, 2016 at 8:42 PM, Jeremy Allison <jra at samba.org> wrote:

--- src/utils.ml | 21 +++++++++++++++++++++ src/utils.mli | 3 +++ 2 files changed, 24 insertions(+) diff --git a/src/utils.ml b/src/utils.ml index 3e81c21..7ae24bd 100644 --- a/src/utils.ml +++ b/src/utils.ml @@ -204,3 +204,24 @@ let compare_architecture a1 a2 = exit 1 in compare (index_of_architecture a1) (index_of_architecture a2) + +(* Parse a size field, eg. "10G".