Package: system-storage-manager
Version: 0.3-1
Severity: important
Tags: upstream
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
(500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages system-storage-manager depends on:
ii btrfs-tools 3.14.1-1
ii cryptsetup-bin 2:1.6.4-4
ii dmsetup 2:1.02.83-2
ii libpython2.7-stdlib [python-argparse] 2.7.6-8
ii lvm2 2.02.104-2
ii python 2.7.5-5
ii xfsprogs 3.1.9
system-storage-manager recommends no packages.
system-storage-manager suggests no packages.
-- no debconf information
It seems that the ssm tool can not work with the changed data format in btrfs
library:
root@tao:~# ssm list volumes
Traceback (most recent call last):
File "/usr/bin/ssm", line 33, in <module>
sys.exit(main.main())
File "/usr/lib/python2.7/dist-packages/ssmlib/main.py", line 1588, in main
args.func(args)
File "/usr/lib/python2.7/dist-packages/ssmlib/main.py", line 1078, in list
self.vol.ptable(more_data=self.dev.filesystems())
File "/usr/lib/python2.7/dist-packages/ssmlib/main.py", line 817, in vol
self._volumes = Volumes(options=self.options)
File "/usr/lib/python2.7/dist-packages/ssmlib/main.py", line 718, in __init__
self._data['btrfs'] = btrfs.BtrfsVolume(options=self.options)
File "/usr/lib/python2.7/dist-packages/ssmlib/backends/btrfs.py", line 226,
in __init__
super(BtrfsVolume, self).__init__(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/ssmlib/backends/btrfs.py", line 102,
in __init__
fs_used = get_real_number(array[6])
File "/usr/lib/python2.7/dist-packages/ssmlib/backends/btrfs.py", line 36, in
get_real_number
number = float(string[0:-2])
ValueError: invalid literal for float(): 1.33G
root@tao:~#
All my volumes use btrfs. The above error occurs each time when I try to run
the ssm command (with any parameter).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
