similar to: corrupted btrfs after suspend2ram uncorrectable with scrub

Displaying 20 results from an estimated 400 matches similar to: "corrupted btrfs after suspend2ram uncorrectable with scrub"

2009 Nov 24
4
[Bug 25265] New: NV30, resume from suspend2ram fails
http://bugs.freedesktop.org/show_bug.cgi?id=25265 Summary: NV30, resume from suspend2ram fails Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2009 Dec 04
7
[Bug 25453] New: nouveau + multiple xorg servers + suspend2ram trashes root partition
http://bugs.freedesktop.org/show_bug.cgi?id=25453 Summary: nouveau + multiple xorg servers + suspend2ram trashes root partition Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: high Component: Driver/nouveau
2012 Aug 15
6
State of nocow file attribute
Hello, some time ago we discussed on #btrfs that the nocow attribute for files wasn''t working (around 3.3 or 3.4 kernels). That was evident by files fragmenting even with the attribute set. Chris mentioned to find a fix quickly for that, and posted some lines of change into irc. But recently someone mentioned that 3.6-rc looks like still not respecting nocow for files. Is there really
2005 Mar 31
1
exclude_dir option for VFS recycle module
Hello all, I am testing the VFS recycle module, and have a question. The module is working the way I hoped with the exception of the exclude_dir option. I have an entry like: exclude_dir = dir1 -- files I place in dir1 are not sent to the recycle location. However, if I have a folder beneath dir1 like dir1/dir2, files in dir2 get sent to the recycle location. I've tried using wildcards in
2010 Feb 20
2
[PATCH] drm/nouveau: fix missing spin_unlock in failure path
Found by sparse. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_gem.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c b/drivers/gpu/drm/nouveau/nouveau_gem.c index 03d8935..d7ace31 100644 --- a/drivers/gpu/drm/nouveau/nouveau_gem.c +++ b/drivers/gpu/drm/nouveau/nouveau_gem.c @@
2010 Feb 26
2
[PATCH] renouveau/nv10: remove duplicate vertex buffer registers
NV10TCL defines the vertex buffer registers both as arrays and as individual named registers. This causes duplicate register definitions and the individual registers are not used either by the DDX or by the Mesa driver. Francisco Jerez said to remove them all. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- renouveau.xml | 49
2010 Jan 16
1
[PATCH] drm/nouveau: Acknowledge DMA_VTX_PROTECTION PGRAPH interrupts
Currently Nouveau is unable to dismiss DMA_VTX_PROTECTION errors, which results in an infinite loop in the interrupt handler. These errors are caused both by bugs in the Gallium driver and by user-specified index buffers with out of bounds indices. By mmio-tracing the nVidia drivers, I found out how this is done. On DMA_VTX_PROTECTION, The nVidia driver reads the register 0x402000, always
2009 Apr 09
7
Btrfs TODO
Hello, Trying to put together a list of TODO items for btrfs so we can update the wiki page fully. So far these things are on the list * Proper ENOSPC handling * O_DIRECT support (without checksumming) * AIO support * Subvolume quotas and inherited space usage information * Snapshot removal * QA Suite for automated regression testing * Reserved space for online fsck and the ability to add
2010 Jan 28
1
[PATCH] drm/nouveau: enlarge GART aperture
This patch enlarges the PCI GART aperture to 512 MB. The current 64MB aperture is too small and should be enlarged. The optimal amound may be card/system-dependent, so a more sophisticated approach may be preferable. In particular, if RAMIN is less than 1MB, a 512MB aperture won't fit. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_sgdma.c
2007 Jan 09
4
Yukon Nic
He Everyone, We found out that till version 3.02 the Yukon nic is supported after it gives code errors, i'm working a lot with ehtherboot via drbl / clonezilla, and together with Steven Shiau we ask you guys if you can arrange that the Yukon can be supported again. Our thanx in advance. Dave & Steven
2000 Feb 16
0
Freak thing happen with my samba!
Hey guys, my SAMBA server is crazy, it only accept connections after I connect to the internet. I tried all your tests, but nothing. the nmblookup is pointing to the right IP, but when I tried to connect with the smbclient or even with my win95 pc I do no get a response, I got this message: [root] samba# smbclient -L K-S_MACHINE -U root -I 127.0.0.1 Added interface ip=192.168.1.1
2011 Aug 26
39
[Bug 40406] New: Nouveau NVIDIA NV46: Freeze
https://bugs.freedesktop.org/show_bug.cgi?id=40406 Summary: Nouveau NVIDIA NV46: Freeze Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: marco
2010 Mar 13
2
[PATCH] nv30/nv40 Gallium drivers unification
Currently the nv30 and nv40 Gallium drivers are very similar, and contain about 5000 lines of essentially duplicate code. I prepared a patchset (which can be found at http://repo.or.cz/w/mesa/mesa-lb.git/shortlog/refs/heads/unification+fixes) which gradually unifies the drivers, one file per the commit. A new "nvfx" directory is created, and unified files are put there one by one.
2010 Feb 01
4
[PATCH 1/3] Introduce nouveau_bo_wait for waiting on a BO with a GPU channel
nouveau_bo_wait will make the GPU channel wait for fence if possible, otherwise falling back to waiting with the CPU using ttm_bo_wait. The nouveau_fence_sync function currently returns -ENOSYS, and is the focus of the next patch. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_bo.c | 68 ++++++++++++++++++++++++++++++-
2010 Aug 12
2
thread locked while flushing to database
On a multicore Linux platform I'm running a simple c test program, to evaluate xapian performance, and inspect advantages in multiple indexing. I'm starting two threads, and each thread writes to his database. main th -> indexing thread_1 -> db1 (dispatcher) -> indexing thread_2 -> db2 I use sched_setaffinity to bind each indexing thread to a specific core.
2007 Mar 12
8
[Bug 1295] [PATCH] Transparent proxy support on Linux
http://bugzilla.mindrot.org/show_bug.cgi?id=1295 Summary: [PATCH] Transparent proxy support on Linux Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy:
2009 Dec 27
2
[Bug 25806] New: NV40 vertex corruption (kernel BO deletion too early?)
http://bugs.freedesktop.org/show_bug.cgi?id=25806 Summary: NV40 vertex corruption (kernel BO deletion too early?) Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org
2010 Jan 18
1
[PATCH] drm/ttm: Fix race condition in ttm_bo_delayed_delete (v2)
ttm_bo_delayed_delete has a race condition, because after we do: kref_put(&nentry->list_kref, ttm_bo_release_list); we are not holding the list lock and not holding any reference to objects, and thus every bo in the list can be removed and freed at this point. However, we then use the next pointer we stored, which is not guaranteed to be valid. This was apparently the cause of some
2008 Feb 14
2
btrfs v0.11 & btrfs v0.12 benchmark results
Hi, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM
2012 Mar 02
1
nocow flags
I set the C (NOCOW) and z (Not_Compressed) flags on a folder but the extent counts of files contained there keep increasing. Said files are large and frequently modified but not changing in size. This does not happen when the filesystem is mounted with nodatacow. I''m using this as a workaround since subvolumes can''t be mounted with different options simultaneously. ie. one with