Bug #20492
Snapshots do not check if drive has been unlocked
Status:
Closed: Duplicate
Priority:
Nice to have
Assignee:
William Grzybowski
Category:
OS
Target version:
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
I added a passphrase to my pool and rebooted... these snapshots failed before I had a chance to unlock the pool. Some check should probably be done to let autosnap fail more gracefully...
Jan 23 15:48:02 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot -r "maindata@auto-20170123.1548-2m"
Jan 23 15:48:02 freenas autosnap.py: [tools.autosnap:506] Failed to create snapshot 'maindata@auto-20170123.1548-2m': cannot open 'maindata': dataset does not exist
usage:
snapshot|snap [-r] [-o property=value] ... <filesystem|volume>@<snap> ...
For the property list, run: zfs set|get
For the delegated permission list, run: zfs allow|unallow
Related issues
History
#1
Updated by nils b about 4 years ago
Updated by nils b https://bugs.freenas.org/issues/7155 has another issue with something not happening at the correct time wrt unlocking pools...
#2
Updated by Kris Moore about 4 years ago
- Assignee set to William Grzybowski
- Priority changed from No priority to Nice to have
- Target version set to 9.10.2-U3
#3
Updated by William Grzybowski about 4 years ago
Updated by William Grzybowski - Status changed from Unscreened to Screened
#4
Updated by Kris Moore about 4 years ago
- Target version changed from 9.10.2-U3 to 9.10.4
#5
Updated by Kris Moore almost 4 years ago
- Target version changed from 9.10.4 to 11.1
#6
Updated by William Grzybowski over 3 years ago
- Status changed from Screened to Closed: Duplicate
#7
Updated by William Grzybowski over 3 years ago
- Has duplicate Bug #24049: Only snapshot imported volumes added
#8
Updated by Dru Lavigne over 3 years ago
Updated by Dru Lavigne - Target version changed from 11.1 to N/A