search for: 382m

...139M 24% /boot /dev/mapper/VolGroup00-DataVol00 39G 16G 22G 42% /data none 157M 0 157M 0% /dev/shm /dev/mapper/VolGroup00-HomeVol00 77G 58G 15G 80% /home /dev/mapper/VolGroup00-VarVol00 16G 382M 15G 3% /var Rather than try and reduce the size of the VarVol00 volume to make more unallocated space which I have heard is a little dangerous.. I would like to get rid of the VarVol00 and have the /var directory on the RootVol00 volume.. Then I can allocate some of the free space to HomeV...

...hard link would. Here is a simple example using 2 small btrfs filesystems on a Gentoo Linux system with current btrfs tools... # I start with 2 empty filesystems... > df -hT /test/*/ Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg-test_btrfs btrfs 1.0G 56K 382M 1% /test/btrfs /dev/mapper/vg-test_rsync btrfs 1.0G 56K 382M 1% /test/rsync # I create a subvolume within the btrfs filesystem > btrfs sub create btrfs/current Create subvolume 'btrfs/current' # I copy 2 mp3 files into the subvolume > cp -v *.mp3 btrfs/current/ `ChangeMe.mp3...

Hi, I am dealing with very large datasets and it takes a long time to save a workspace image. The options to save compressed data are: "gzip", "bzip2" or "xz", the default being gzip. I wonder if it's possible to include the pbzip2 (http://compression.ca/pbzip2/) algorithm as an option when saving. "PBZIP2 is a parallel implementation of the bzip2