Re: Problem with btrfsck / couurpted filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 27, 2013 at 04:23:45PM +0200, Stéphane Mutz wrote:
> Hi,
> 
> I've built the GIT tools and run btrfsck (without options) following the
> wiki page.
> I got the following log:
> Checking filesystem on /dev/VG_NL-SAS/LV_snap
> UUID: de300fd0-1251-4767-9d80-84ce7ebfba9a
> checking extents
> checking free space cache
> free space inode generation (0) did not match free space cache
> generation (16583)
> free space inode generation (0) did not match free space cache
> generation (16579)
> checking fs roots
> checking csums
> checking root refs
> found 120489896006 bytes used err is 0
> total csum bytes: 380818020
> total tree bytes: 10396295168
> total fs tree bytes: 9423839232
> total extent tree bytes: 473616384
> btree space waste bytes: 1923163802
> file data blocks allocated: 455172272128
>  referenced 564086325248
> Btrfs v0.20-rc1-335-gf00dd83
> 
> It does not report any extends error.
> Can I consider all is fine now?
> 

Yup.  If you still have problems its likely just a kernel bug and not a
corruption problem.  And if that's the case dmesg would be nice so we can see
whats going on.  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux