Hi Denis,
Zitat von Denis Bychkov <manover@xxxxxxxxx>:
Why is it so important to grow the backing device online, without even
re-registering it? It should it be enough to unmount whatever FS is on
top of it, unregister the device and register it again to "resize" it.
(Or reboot the system for that matter). Is there really a pressuring
need to do it on the fly?
from a professional standpoint, rebooting a SAN server just to have
some subsystem recognize the increase in available space is a huge
step backwards. As a matter of fact, in the chain of hardware - MDRAID
- bcache - LVM - FS - NFS / SMB / SCST, bcache is the only component
that requires to take the service offline (by umount / reboot). Yes,
there is such a need.
On Tue, Dec 22, 2015 at 6:40 AM, Jens-U. Mozdzen <jmozdzen@xxxxxx> wrote:
Hi,
an earlier, similar question went by unanswered, so let me give it another
try:
I have set up a bcache device on top of DMRAID devices for cache and backing
device.
While I can dynamically resize both RAIDs, the bcache device will not catch
up with the changes "live". This conforms to what Kent wrote in 2012
(http://comments.gmane.org/gmane.linux.kernel.bcache.devel/249):
--- cut here ---
For the backing device, I think things will just work - you'll just
have to close and reopen the backing device in order for bcache to
notice the new size. Bcache's superblock doesn't remember the size, it
just goes off of what the size of the backing device is when it's
registered.
There's currently no way to make bcache notice the backing device has
grown to do it at runtime, though that ought to be fairly simple too.
--- cut here ---
If this currently is still not implemented, has anyone started to work on
some "resizebcache" tool, if only handling the backing device?
Regards,
Jens
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
