- Code: Select all
macbookpro08-centrim:~ gjp22$ zpool add gjp22 cache /dev/disk3
could not create pool: permission denied
macbookpro08-centrim:~ gjp22$ sudo zpool add gjp22 cache /dev/disk3
Password:
Then, on entry of the password, forced unmount of the file systems of the pool.
The force took me by surprise:
- no -f in the command
- in the man page (missing its Cache Devices section), no hint that addition requires an unmount.
- Code: Select all
2013-03-24 10:29:51.678 sudo[26827]: gjp22 : TTY=ttys003 ; PWD=/Volumes/gjp22 ; USER=root ; COMMAND=/usr/sbin/zpool add gjp22 cache /dev/disk3
2013-03-24 10:29:53.000 kernel[0]: ZFSLabelScheme:willTerminate: this 0xffffff802eaa0900 provider 0xffffff802dfda600 '%noformat%'
2013-03-24 10:29:53.000 kernel[0]: ZFSLabelScheme:stop: 0xffffff802eaa0900 goodbye '%noformat%'
2013-03-24 10:29:57.000 kernel[0]: ZFSLabelScheme:probe: label '???', vdev 17043972105408950164
2013-03-24 10:29:57.000 kernel[0]: zfsx_unmount: '/opt' forced (umount)
2013-03-24 10:30:08.000 kernel[0]: zfsvfs_teardown: '/opt' (txg_wait_synced in 11017 ms)
2013-03-24 10:30:08.000 kernel[0]: zfsx_unmount: '/Volumes/gjp22/casesensitive' forced (umount)
2013-03-24 10:30:12.000 kernel[0]: ZFSLabelScheme::terminate(kIOServiceSynchronous) timeout
2013-03-24 10:30:12.000 kernel[0]: zfsvfs_teardown: '/Volumes/gjp22/casesensitive' (txg_wait_synced in 4547 ms)
2013-03-24 10:30:21.000 kernel[0]: zfsx_unmount: '/Volumes/gjp22' forced (umount)
gjp22 is my home directory so the unmount was disruptive. But not disastrous – I used the key chord for sysdiagnose then remotely with ssh, I observed a full send and receive (two other pools), which had begun before the unmount issue, complete without error. Then sudo shutdown -r now got as far as it could and I forced a restart (Control-Command-Power).
Question
Is it normal for addition of a cache vdev to require unmount of the pool's file systems?