byobu disk_io script cannot handle cryptsetup, LVM, and other DM-based volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
byobu (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
affects ubuntu/byobu
status triaged
In a nutshell:
% /usr/lib/
awk: cmd. line:1: fatal: cannot open file `/sys/block/
reading (No such file or directory)
% ls /sys/block
dm-0@ dm-2@ loop0@ loop2@ loop4@ loop6@ ram0@ ram10@ ram12@ ram14@
ram2@ ram4@ ram6@ ram8@ sda@ zram1@
dm-1@ dm-3@ loop1@ loop3@ loop5@ loop7@ ram1@ ram11@ ram13@ ram15@
ram3@ ram5@ ram7@ ram9@ zram0@
% ls -l /dev/mapper
total 0
crw------- 1 root root 10, 236 2011-01-21 00:09 control
lrwxrwxrwx 1 root root 7 2011-01-21 00:09 cryptostuff -> ../dm-0
lrwxrwxrwx 1 root root 7 2011-01-21 00:09 cryptostuff-home -> ../dm-3
lrwxrwxrwx 1 root root 7 2011-01-21 00:09 cryptostuff-root -> ../dm-1
lrwxrwxrwx 1 root root 7 2011-01-21 00:09 cryptostuff-swap -> ../dm-2
lrwxrwxrwx 1 root root 7 2011-01-24 00:57 temporary-
../dm-4
lrwxrwxrwx 1 root root 7 2011-01-26 08:09 temporary-
../dm-8
Basically, resolving the symlinks down to the actual device should solve the
issue. I've attached a patch which appears to do just that.
--
Kind regards,
Loong Jin
tags: | added: patch |
Awesome, thanks for the patch! I just committed the same change moments ago ;-)
Cheers!