Description of problem: --- bcache --- Device /dev/bcache0 (253:0) UUID 29f194ce-a39e-44ec-a650-f9f20b5d2ac7 Block Size 0.50KiB Bucket Size 512.00KiB Congested? False Read Congestion 2.0ms Write Congestion 20.0ms Total Cache Size 476.94GiB Total Cache Used 476.94GiB (100%) Total Cache Unused 0B (0%) Traceback (most recent call last): File "bcache-stabcache-status-20130825/bcache-status", line 348, in <module> main() File "bcache-stabcache-status-20130825/bcache-status", line 341, in main dump_bcache('%s%s' % (SYSFS_BCACHE_PATH, cache), stats, print_subdevices, uuid_map.get(cache, '?')) File "bcache-stabcache-status-20130825/bcache-status", line 242, in dump_bcache val = conversion_func(val) File "bcache-stabcache-status-20130825/bcache-status", line 209, in <lambda> ('dirty_data', 'Dirty Data', lambda x: fmt_cachesize(interpret_sectors(x))), File "bcache-stabcache-status-20130825/bcache-status", line 75, in interpret_sectors if x[-1] in factors: IndexError: string index out of range Version-Release number of selected component (if applicable): How reproducible: 100% with writearound (on Debian though) Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Quick patch: $ diff bcache-status bcache-status.RPR 74a75,76 > if len(x) == 0: > return 0
Nevermind, I had an older version. The newer version doesn't look at the dirty_data entry any more. *** This bug has been marked as a duplicate of bug 1066555 ***