-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Received filesystems is mounted in bulk when the whole receive is finished instead of individually when received #2673
Comments
mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…been received Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…been received Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…been received Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Do you mount filesystems after the recv for it is complete, or on every snapshot received (send -i/I) ? |
I can think of a why this is a bad idea. When receiving in bulk the mountpoint properties may be set. You should wait until the end before mounting to ensure you can honour mount point dependencies. |
But in that case couldn't we sort the datasets into an appropriate receive order that would allow the mountpoint property to be honored, in the exact same way we already do so when sorting the datasets into an unmount order that will allow all the datasets to unmount successfully when exporting? |
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
…eived Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Instead of storing the filesystem just received in top_zfs, mount and share it directly in zfs_receive_one(). This will make a filesystem be mounted as soon as it's been received, instead of waiting to the very end - which might take days. Signed-off-by: Turbo Fredriksson <[email protected]> Closes: openzfs#2673
Closing, won't fix. As was mentioned above we should wait until to end before mounting to ensure to mount point dependencies are honored. |
Sending 4TB and 174 filesystems takes a while and the mount happens when all 174 is transfered.
It would be better/nicer if each filesystem was mounted after it have been transfered instead of waiting two days...
The text was updated successfully, but these errors were encountered: