The below is from a system running the Debian kernel 3.2.0-4-amd64 on a 120G
Intel SSD. What would these 2 errors be?
scrub device /dev/disk/by-uuid/7939c405-c656-4e85-a6a0-29f17be09585 (id 1)
done
scrub started at Thu Jan 10 06:00:02 2013 and finished after 295
seconds
total bytes scrubbed: 25.42GB with 2 errors
error details: super=2
corrected errors: 0, uncorrectable errors: 0, unverified errors: 0
I know you all recommend later kernels, I''m upgrading things as fast as
I can.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Jan 10, 2013 at 11:38:45AM +1100, Russell Coker wrote:> The below is from a system running the Debian kernel 3.2.0-4-amd64 on a 120G > Intel SSD. What would these 2 errors be? > > scrub device /dev/disk/by-uuid/7939c405-c656-4e85-a6a0-29f17be09585 (id 1) > done > scrub started at Thu Jan 10 06:00:02 2013 and finished after 295 > seconds > total bytes scrubbed: 25.42GB with 2 errors > error details: super=2 > corrected errors: 0, uncorrectable errors: 0, unverified errors: 0Looks like broken superblocks, from that message. There''s probably more information in your kernel logs.> I know you all recommend later kernels, I''m upgrading things as fast as I can.Glad to hear it. :) Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- We believe in free will because we have no choice. ---
On Thu, 10 Jan 2013, Hugo Mills <hugo@carfax.org.uk> wrote:> Looks like broken superblocks, from that message. There''s probably > more information in your kernel logs.The only BTRFS message I see in the kernel log is "btrfs: unlinked 3 orphans" which happens every time a cron job makes a snapshot of /home. Why does it do that? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Jan 10, 2013 at 11:38:45AM +1100, Russell Coker wrote:> The below is from a system running the Debian kernel 3.2.0-4-amd64 on a 120G > Intel SSD. What would these 2 errors be? > > scrub device /dev/disk/by-uuid/7939c405-c656-4e85-a6a0-29f17be09585 (id 1) > done > scrub started at Thu Jan 10 06:00:02 2013 and finished after 295 > seconds > total bytes scrubbed: 25.42GB with 2 errors > error details: super=2The superblock errors are detected but not corrected right away, because next transaction commit will overvrite it. Does scub report the errors repeatedly? There are no other scrub errors reported, I guess there are also no relevant messages in syslog. During transaction commit scrub is paused, so it''s not possible to verify a half-made superblock.> corrected errors: 0, uncorrectable errors: 0, unverified errors: 0david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 10 Jan 2013, David Sterba <dsterba@suse.cz> wrote:> > total bytes scrubbed: 25.42GB with 2 errors > > error details: super=2 > > The superblock errors are detected but not corrected right away, because > next transaction commit will overvrite it. > > Does scub report the errors repeatedly?Scrub reported the errors repeatedly, but now the errors have gone away (I have just done a few scrubs with no errors reported). So it seems that something that happened in the mean time fixed it. Thanks for your reply. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html