linux-kernel - Resizing block devices that are in use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 12 Nov 2008 19:44:07 +0200
From:	Lasse Kärkkäinen <tronic+bpsk@....iki.fi>
To:	linux-kernel@...r.kernel.org
Subject: Resizing block devices that are in use

Currently the kernel does not seem to resize SCSI devices when rescan is 
done, if the device is in use (e.g. there's a filesystem mounted on it). 
Additionally, it also won't resize it if rescan (changing size in 
hardware) is done first while mounted and then the device is unmounted, 
even if rescan is attempted again.

Steps to reproduce:
1. mount a filesystem on a SCSI device
2. resize the disk (e.g. grow hardware RAID array)
3. echo 1 > "/sys/bus/scsi/devices/0:0:1:0"
4. unmount the filesystem
5. echo 1 > "/sys/bus/scsi/devices/0:0:1:0" again
6. the size of the device (e.g. /dev/sdb) still hasn't changed

A preferrable solution (to me) would be to resize the device as soon as 
rescan is done, no matter if it is in use or not. It will fix the bug 
and the "feature" both at the same time.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/