From: Wang Shilong wangsl.f...@cn.fujitsu.com
I can easily trigger the following warnings when enabling quota
in my virtual machine(running Opensuse), Steps are firstly creating
a subvolume full of fragment extents, and then create many snapshots
(500 in my test case).
[ 2362.808459] BUG: soft
When it rains it pours. My other array is having some issues. I
think I have two problems, and wondering if someone can help me make
sense of this:
I've basically got four questions:
1. How do I repair, or drop block 35435896033280?
2. How do I identify which drive out of 5 this block is
Martin Steigerwald posted on Sat, 25 Jan 2014 15:01:13 +0100 as excerpted:
Am Samstag, 25. Januar 2014, 15:33:08 schrieb Imran Geriskovan:
Every write on a SSD block reduces its data retension capability.
No concrete figures but it is assumed to be - 10 years for new devices
- 1 year at
On 01/25/2014 01:59 AM, Wang Shilong wrote:
From: Wang Shilong wangsl.f...@cn.fujitsu.com
We are really suffering from now ulist's implementation, some developers
gave their try, and i just gave some of my ideas for things:
1. use list+rb_tree instead of arrary+rb_tree
2. add cur_list to
G. Michael Carter posted on Sun, 26 Jan 2014 10:11:08 -0500 as excerpted:
I've basically got four questions:
1. How do I repair, or drop block 35435896033280?
2. How do I identify which drive out of 5 this block is on?
3. How do I detect which drive is causing the errno=-5 IO failure
Martin Steigerwald posted on Sat, 25 Jan 2014 13:54:40 +0100 as excerpted:
Hi Duncan,
Am Freitag, 24. Januar 2014, 06:54:31 schrieb Duncan:
Anyway, yes, I turned autodefrag on for my SSDs, here, but there are
arguments to be made in either direction, so I can understand people
choosing not
Most consumer drives have bad sector timeouts that aren't configurable, and are
in the ~120 second realm. The kernel puts a SCSI command timer on each command,
which by default is 30 seconds. This mismatch means drives can develop bad
sectors that can't be recovered, because the kernel resets
Please report the kernel and btrfs-progs versions, and the result from
# btrfs fi df /mnt/bt_store
Bad blocks typically cause two error messages: read error, link reset. The
first is an error from the drive itself and will include the affected LBAs. The
second is the result of linux SCSI
On 27 January 2014 12:18, Sachin Kamat sachin.ka...@linaro.org wrote:
PTR_RET is deprecated. Use PTR_ERR_OR_ZERO instead. While at it
also include missing err.h header.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
Please note, there is no second patch in this series. Sorry for the
PTR_RET is deprecated. Use PTR_ERR_OR_ZERO instead. While at it
also include missing err.h header.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
fs/btrfs/root-tree.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/root-tree.c b/fs/btrfs/root-tree.c
10 matches
Mail list logo