Occasional read error on idle USB attached disk

x86_64 Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz GenuineIntel GNU/Linux -- Sandy McArthur, Jr. No nation could preserve its freedom in the midst of continual warfare. - Letters and Other Writings of James Madison (1865), Vol. IV, p. 491 -- To unsubscribe from this list: send the line unsubscribe

What does scrub tell me?

].corruption_errs 2 -- Sandy McArthur He who dares not offend cannot be honest. - Thomas Paine -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: btrfs scrub status reports not running when it is

corrected errors: 512, uncorrectable errors: 1, unverified errors: 0 Still, the output when wrapping up is still not intuitive to me: scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136982 seconds, not running On Wed, Jan 14, 2015 at 4:06 PM, Sandy McArthur Jr sandy...@gmail.com wrote

btrfs scrub status reports not running when it is

errors error details: verify=19 csum=494 corrected errors: 512, uncorrectable errors: 1, unverified errors: 0 # uname -a Linux mcplex 3.18.2-gentoo #1 SMP Mon Jan 12 10:24:25 EST 2015 x86_64 Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz GenuineIntel GNU/Linux # btrfs --version Btrfs v3.18.1 -- Sandy

Re: If btrfs-find-root doesn't find tree roots is the filesystem lost?

On Sun, Dec 7, 2014 at 12:50 AM, Sandy McArthur Jr sandy...@gmail.com wrote: Would the `btrfs check` output below indicate only small error and that a --repair is likely to succeed? It did. Thanks Qu and Duncan. dmesg suggests I have some scrubbing to do: [220283.369150] BTRFS: bdev /dev/sdh1

Re: If btrfs-find-root doesn't find tree roots is the filesystem lost?

...@cn.fujitsu.com wrote: Original Message Subject: If btrfs-find-root doesn't find tree roots is the filesystem lost? From: Sandy McArthur Jr sandy...@gmail.com To: linux-btrfs@vger.kernel.org linux-btrfs@vger.kernel.org Date: 2014年12月04日 09:20 I have a many-disk btrfs filesystem that I

If btrfs-find-root doesn't find tree roots is the filesystem lost?

lines] -- Sandy McArthur -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Working on Btrfs as topic for master thesis

have either the time or the skills with kernel programming that would be needed). Maybe this happens already: Might a similar effect be automatically achieved by tracking per-device I/O load averages and distributing reads based on the I/O loads of possible read devices? -- Sandy McArthur

Re: Help interpreting RAID1 space allocation

temporarily. That said my biggest btrfs problem happened while I had some drives on SATA and others on USB. -- Sandy McArthur -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org

Re: Recovery advice

balance has been run successfully and completely. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Sandy McArthur He who dares not offend cannot

filefrag and btrfs filesystem defragment and maybe snapshots

improve these files? I do have a number rolling readonly snapshots on the subvolume these files are on. I can imagine how that might be related but I'm not sure. When the pre-defrag snapshots are purged will the filefrag extents count drop. -- Sandy McArthur He who dares not offend cannot

Re: filefrag and btrfs filesystem defragment and maybe snapshots

On Thu, Aug 1, 2013 at 10:27 PM, Duncan 1i5t5.dun...@cox.net wrote: Sandy McArthur posted on Thu, 01 Aug 2013 17:18:50 -0400 as excerpted: While exploring some btrfs maintenance with respect to defragmenting I ran the following commands: # filefrag /path/to/34G.file /path/to/5.7G.file /path

Recovery advice

where all I can think to do is wipe disk 4 and then add it back in. Is there anything else I should try first. I have booted btrfs-next with the latest btrfs-progs. Thanks. -- Sandy McArthur He who dares not offend cannot be honest. - Thomas Paine -- To unsubscribe from this list: send the line

Re: Different size devices in RAID

to read from the slowest drive that would likely be your bottleneck for that read. Another drive arrived today, I'll see what happens when I mix/match USB3 and SATA connected drives. -- Sandy McArthur He who dares not offend cannot be honest. - Thomas Paine -- To unsubscribe from this list: send

Re: bug: corrupt filesystem, cannot delete tmp files created just before crash.

I specified for no changes to be attempted. This would have saved me time and the emotional grief of my perceiving that my problems were persisting a btrfsck. On Wed, Jul 17, 2013 at 7:38 PM, Duncan 1i5t5.dun...@cox.net wrote: Sandy McArthur posted on Wed, 17 Jul 2013 10:06:05 -0400 as excerpted

Re: bug: corrupt filesystem, cannot delete tmp files created just before crash.

System, RAID1: total=8.00MB, used=132.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=2.00GB, used=1.13GB Metadata: total=8.00MB, used=0.00 On Thu, Jul 18, 2013 at 10:19 AM, Sandy McArthur sandy...@gmail.com wrote: I was able to recover the filesystem using the btrfsck from git (Btrfs

bug: corrupt filesystem, cannot delete tmp files created just before crash.

by a `rm /path/to/busted/tmp-file` from different kernel versions as they look different enough to me to possibly be helpful. I'm happy to provide whatever other info is needed. An image of the filesystem isn't so practical as it's large. -- Sandy McArthur He who dares not offend cannot be honest