Skip to content
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

Closed
FransUrbo opened this issue Sep 7, 2014 · 4 comments

Comments

@FransUrbo
Copy link
Contributor

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...

FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 7, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 7, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 8, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 10, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 12, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 14, 2014
…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
@GregorKopka
Copy link
Contributor

Do you mount filesystems after the recv for it is complete, or on every snapshot received (send -i/I) ?

@DeHackEd
Copy link
Contributor

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.

@ilovezfs
Copy link
Contributor

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?

FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 16, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 18, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 22, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 22, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 27, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Sep 30, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Oct 3, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Oct 11, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Oct 19, 2014
…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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Nov 5, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Nov 5, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Nov 6, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Nov 7, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Dec 6, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Dec 19, 2014
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Feb 7, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Mar 15, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Mar 29, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Mar 30, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Mar 30, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Apr 21, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue May 3, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue May 17, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jun 10, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jun 11, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jul 22, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jul 24, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jul 24, 2015
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
FransUrbo added a commit to FransUrbo/zfs that referenced this issue Jul 31, 2015
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
@behlendorf
Copy link
Contributor

Closing, won't fix. As was mentioned above we should wait until to end before mounting to ensure to mount point dependencies are honored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants