Re: Several unhappy btrfs's after RAID meltdown

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

 



On 15 Nov 2012 10:00 -0600, from nemesis-lists@xxxxxxxxxxxx (Ryan C. Underwood):
> There is still a lot of data missing though.  If I am reading this
> correctly there was about 300GB of data which compressed to 254GB
> on-disk.
> 
> Label: 'vicep-library'  uuid: 89b14d35-b31a-4fbe-a2d9-cb83cbcd3851
>         Total devices 1 FS bytes used 254.35GB
>         devid    1 size 1.00TB used 299.04GB path /dev/dm-27

Isn't that the other way around? The file system has allocated a total
of 299 GB across devid 1 (to system, metadata and data), and of those,
254 GB are in actual use currently. Remember btrfs "overallocates" so
it doesn't have to constantly allocate more space for each separate
kind of usage as data is added to the file system.

That does not radically alter your conclusion, though. 36 GB is still
only a small fraction of the total amount of data stored, assuming
that the btrfs tool output you showed can be trusted.

-- 
Michael Kjörling • http://michael.kjorling.se • michael@xxxxxxxxxxx
                “People who think they know everything really annoy
                those of us who know we don’t.” (Bjarne Stroustrup)
--
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