On 01/13/2011 03:30 PM, Tejun Heo wrote: Hi, >> Anyway, it is /sys/block - so it represents block devices. >> >> If btrfs internally creates some virtual _block_ device for its pool, it should >> present it here too with slaves/holders. If not, why it should create any links there? > > Yeah, that's the most bothering part for me. The biggest customers of > bd_claim are filesystems and all these custom symlinkeries don't do > nothing for them. It just doesn't make a whole lot of sense to me. Well, then it is not optimal for fs and should it be separated? There is also /sys/fs now... I think represent dependences of block devices in some generic (and exactly defined) way is useful. So if there is something missing, lets define it properly. The whole idea behind lsblk was practical: we responded many questions why "device is busy" and what keeps it open in stacked subsystem. Just try fdisk, mdadm, dmsetup table, losetup -a, kpartx, cryptsetup, etc ... So listing block device tree using ONE interface (sysfs) to check and display device tree for ALL subsystems seems to be good idea for me. In this exactly defined case. I am not saying that symlinks are perfect, just that generic interface here is not superfluous. Thanks, Milan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
