Project

General

Profile

Bug #60471

Prevent Cloud Sync Tasks from overflowing /mnt

Added by Dru Lavigne almost 2 years ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Configuring a cloud sync task has the potential to fill the /mnt directory, therefore disallowing the ability to import your zpools.
PR: https://github.com/freenas/freenas/pull/2035


Related issues

Copied from FreeNAS - Umbrella #55899: Prevent Cloud Sync Tasks from overflowing /mntDone

History

#1 Updated by Dru Lavigne almost 2 years ago

  • Copied from Umbrella #55899: Prevent Cloud Sync Tasks from overflowing /mnt added

#3 Updated by Bonnie Follweiler over 1 year ago

  • Needs QA changed from Yes to No

Acceptance Criteria

Create pool /mnt/tank. Create a PULL cloud sync, run it. It should run OK.

Destroy pool /mnt/tank. There should be no directory /mnt/tank. Run cloud sync. It should say "directory does not exist"

Run mkdir /mnt/tank (but do not create pool). Run cloud sync. It should say "directory must reside within volume mount point"

Test passed in TrueNAS-11.1-U7-INTERNAL3

#4 Updated by Bonnie Follweiler over 1 year ago

  • Status changed from Ready for Testing to Passed Testing

#5 Updated by Jeff Ervin over 1 year ago

47820
47827
47829

Test Passed FreeNAS-11.1-U7-INTERNAL1

Used Acceptance Criteria (wording for part 3 of the criteria is not exactly same as wording within the system, but still passed as it stated the same thing - see screenshot)

#6 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF