similar to: Data corruption with samba 2.2.1a (resolved)

Displaying 20 results from an estimated 100000 matches similar to: "Data corruption with samba 2.2.1a (resolved)"

2001 Sep 30
0
Data corruption with samba 2.2.1a
I've been using Samba 2.0.7-4 (Redhat RPM) successfully on a Linux machine to share files with a few Win2K clients. Just recently I compiled and installed Samba 2.2.1a. It seemed to work fine for a while, but occasionally one of the Windows machines would save a corrupted file to the server... This mainly happened with a Windows 3D rendering program I use, which periodically saves 1MB image
2015 Nov 15
6
[Bug 92959] New: [NV1F celcius GeForce4 MX] Rendering artifacts, screen corruption, system reset.
https://bugs.freedesktop.org/show_bug.cgi?id=92959 Bug ID: 92959 Summary: [NV1F celcius GeForce4 MX] Rendering artifacts, screen corruption, system reset. Product: Mesa Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium
2015 Apr 22
3
[Bug 90145] New: [NV94] Corruption on very long (vertical) pages in Firefox
https://bugs.freedesktop.org/show_bug.cgi?id=90145 Bug ID: 90145 Summary: [NV94] Corruption on very long (vertical) pages in Firefox Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2012 Apr 25
2
[Bug 49142] New: [NV4A] OpengGL content corruption when width >= 2048
https://bugs.freedesktop.org/show_bug.cgi?id=49142 Bug #: 49142 Summary: [NV4A] OpengGL content corruption when width >= 2048 Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component:
2014 Feb 23
0
nouveau graphical corruption in 3.13.2
On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman <daniel at quora.org> wrote: > On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >>> Interestingly, there was graphical failure booting 3.6.11, even >>> nvidia-current fails to initialise, but these
2014 Feb 23
3
nouveau graphical corruption in 3.13.2
On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Interestingly, there was graphical failure booting 3.6.11, even >> nvidia-current fails to initialise, but these two issues could be due >> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>
2020 Apr 27
0
io_uring cause data corruption
On Mon, Apr 27, 2020 at 11:21:35PM +0200, A L wrote: > On 2020-04-27 18:45, Jeremy Allison via samba wrote: > > On Mon, Apr 27, 2020 at 10:27:17AM +0200, A L via samba wrote: > > > On 2020-04-26 19:46, Jeremy Allison via samba wrote: > > > > On Sun, Apr 26, 2020 at 11:51:42AM +0200, A L via samba wrote: > > > > > * Connected from a Windows 10 computer
2017 Oct 11
0
data corruption - any update?
Just to clarify as i'm planning to put gluster in production (after fixing some issue, but for this I need community help): corruption happens only in this cases: - volume with shard enabled AND - rebalance operation In any other cases, corruption should not happen (or at least is not known to happen) So, what If I have to replace a failed brick/disks ? Will this trigger a rebalance and
2023 Mar 03
0
+ ocfs2-fix-data-corruption-after-failed-write.patch added to mm-hotfixes-unstable branch
The patch titled Subject: ocfs2: fix data corruption after failed write has been added to the -mm mm-hotfixes-unstable branch. Its filename is ocfs2-fix-data-corruption-after-failed-write.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/ocfs2-fix-data-corruption-after-failed-write.patch This patch will later
2015 Feb 05
1
[patch] vhost/scsi: potential memory corruption
This code in vhost_scsi_make_tpg() is confusing because we limit "tpgt" to UINT_MAX but the data type of "tpg->tport_tpgt" and that is a u16. I looked at the context and it turns out that in vhost_scsi_set_endpoint(), "tpg->tport_tpgt" is used as an offset into the vs_tpg[] array which has VHOST_SCSI_MAX_TARGET (256) elements so anything higher than 255 then it
2015 Feb 05
1
[patch] vhost/scsi: potential memory corruption
This code in vhost_scsi_make_tpg() is confusing because we limit "tpgt" to UINT_MAX but the data type of "tpg->tport_tpgt" and that is a u16. I looked at the context and it turns out that in vhost_scsi_set_endpoint(), "tpg->tport_tpgt" is used as an offset into the vs_tpg[] array which has VHOST_SCSI_MAX_TARGET (256) elements so anything higher than 255 then it
2020 Apr 27
0
io_uring cause data corruption
On Mon, Apr 27, 2020 at 10:27:17AM +0200, A L via samba wrote: > > On 2020-04-26 19:46, Jeremy Allison via samba wrote: > > On Sun, Apr 26, 2020 at 11:51:42AM +0200, A L via samba wrote: > > > * Connected from a Windows 10 computer over 1G ethernet. * Copy data > > > using Windows Explorer and FastCopy(1) from the Samba share to a > > > local disk. * Verify
2017 Oct 11
2
data corruption - any update?
> corruption happens only in this cases: > > - volume with shard enabled > AND > - rebalance operation > I believe so > So, what If I have to replace a failed brick/disks ? Will this trigger > a rebalance and then corruption? > > rebalance, is only needed when you have to expend a volume, ie by > adding more bricks ? That's correct, replacing a brick
2007 May 29
2
data corruption on AMD AM2 systems with 4GB of RAM or more
Anybody know if the fix for the incorrect kernel behaviour that leads to data corruption will be available for RHEL4/5 kernels?
2005 Aug 29
1
Data corruption
We used rsync 2.6.3 on a couple of Solaris 8 machines to update an Oracle database from one machine to another. Here is the procedure I used: The source database was up and running so this operation was similar to doing a hot backup. I queried the source database for a list of tablespace names, and for each tablespace, I queried the list of datafiles. I put the tablespace in hot backup mode,
2014 Mar 25
12
[Bug 76605] New: Screen corruption and crashes in bastion on NVS-140M (G86)
https://bugs.freedesktop.org/show_bug.cgi?id=76605 Priority: medium Bug ID: 76605 Assignee: nouveau at lists.freedesktop.org Summary: Screen corruption and crashes in bastion on NVS-140M (G86) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: matthias at blankertz.org
2023 Mar 28
0
Patch "ocfs2: fix data corruption after failed write" has been added to the 5.10-stable tree
This is a note to let you know that I've just added the patch titled ocfs2: fix data corruption after failed write to the 5.10-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-fix-data-corruption-after-failed-write.patch and it can be found in the queue-5.10 subdirectory. If
2023 Mar 28
0
Patch "ocfs2: fix data corruption after failed write" has been added to the 5.4-stable tree
This is a note to let you know that I've just added the patch titled ocfs2: fix data corruption after failed write to the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-fix-data-corruption-after-failed-write.patch and it can be found in the queue-5.4 subdirectory. If
2018 May 30
0
shard corruption bug
https://docs.gluster.org/en/latest/release-notes/3.12.6/ The major issue in 3.12.6 is not present in 3.12.7. Bugzilla ID listed in link. On May 29, 2018 8:50:56 PM EDT, Dan Lavu <dan at redhat.com> wrote: >What shard corruption bug? bugzilla url? I'm running into some odd >behavior >in my lab with shards and RHEV/KVM data, trying to figure out if it's >related. >
2012 Jan 31
1
RAM failure led to data corruption
Hi! Today I encountered data corruption on two zfs pools due to a RAM failure in my OI box running on a dell T710. My rpool now looks like this (after reboot): pool: rpool state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire