search for: corrputing

Hello all! I'm with problems with samba 3.6.6. The same happens with 3.6.5, and the upgrade do not helps. Samba is corrupting/removing files in my shares. All happenns like in this bug report, where is attached the smb.conf and another informations about the bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682810 I really don't know what can I do now to solve this, and I'm

Hi, I have been seeing data corruption on the ZFS filesystem. Here are some details. The machine is running s10 on X86 platform with a single 160Gb SATA disk. (root on s0 and zfs on s7) ...Sanjaya --------- /etc/release ---------- -bash-3.00# cat /etc/release Solaris 10 6/06 s10x_u2wos_09a X86 Copyright 2006 Sun Microsystems, Inc. All Rights

Folks, the rgl 0.91 binary for windows seems corrputed. WinZip complains the downloaded zip file is not a valid archive. I had no luck with R-forge either. Could someone point me to the latest production ready binary? Thks. H [[alternative HTML version deleted]]

It is good to see this ----- Forwarded message from syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> ----- Date: Sat, 25 Mar 2017 05:54:09 -0700 From: syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> To: Syslinux commits mailing list <syslinux-commits at zytor.com> Cc: ams at ludd.ltu.se Subject: [syslinux:master] mbr/isohdpfx.S: correct pointer for heads/sectors

...rs on the stack */ mulw %cx /* Heads*sectors -> sectors per cylinder */ pushw %bx /* -20: EBIOS flag */ Given David's last report the part: - jmp 1f + jmp 2f 1: + xor %cx, %cx /* Clear EBIOS flag. */ +2: can be ignored. His BIOS isn't corrputing CX (which I thought). However that part doesn't hurt if it remains. -- MartinS

Hi, Martin Str|mberg wrote: > Given David's last report the part: > - jmp 1f > + jmp 2f > 1: > + xor %cx, %cx /* Clear EBIOS flag. */ > +2: > > can be ignored. His BIOS isn't corrputing CX (which I > thought). However that part doesn't hurt if it remains. I think it still has good reason to exist. The test cmpw $0xaa55, %bx jne 1f could cause a jump which could push a non-zero CX to the stack. (Whatever reason there might be not to get the 0xaa55 signature but to get...

My Server is running 4.5.1 on Ubuntu 16.04, most of the shares are located on a zfs raid. Some of the added profiles are now getting corrputed and cannot login anymore due to some files in the profile share not being accessible After searching online I found two solutions: a) setting aclmode=passthrough, aclinherit=passthrough on the zfs volume b) using nt4 acl mode and the vfs_zfsacl module on

Hello out there, recently I posted a trouble report about my Samba/btrieve experience. I have encountered the worst case scenario - corrupt databases... I had a brief correspondency with Dave Collier-Brown (whose book on Samba can't be praised enough) about this, in which he told me that working under the same login a) network-wide and b) application-wide could lead to such corrpution.

Greetings Everyone, A group in my office is designing/integrating what I would loosly label as an "embedded system". In that, it performs a dedicated task and is not a general purpose workstation or server. It operates in a harsh environment, particularly a questionable power environment and they are extremely concerned about inadvertent shutdown and recovery. They were totally

Hi! I was testing 2.6.0-test5, but got lots of journal aborted errors. Then I Sysrq-s/u/b and wanted to boot 2.4.23-pre3 or 2.4.22, but ext3 error: cannot find root fs cannot mount because of unsupported optional feature (4) after trying to mount it with ext2 (rootfstype=ext2, not working) I rebooted again into 2.4.22, this time there was just severe fs corrpution, illegal blocks, inodes,

vince@rti.com (Vince Chen) write: >We upgraded from samba 1.9.17 to 1.9.18 (now running p7) in hopes of >solving file-corruption problems when large files are copied to >NT from our IRIX 6.2 samba server. > >Has anyone see any file corruption? This won't solve your problem, but I just ran some tests copying a large file from NT to FreeBSD2.2.6 and back, w/o any sign of