jenksdrummer
Patron
- Joined
- Jun 7, 2011
- Messages
- 250
Hello; 13U5.3 Core
I have a 2TB NVMe that I have set as my L2ARC.
I had set L2ARC persistence with the tunable vfs.zfs.l2arc.rebuild_enabled = 1 : SYSCTL; and managed to fill it while doing a lot of IO (hindsight I should have removed the Cache VDEV beforehand, but oh well)
I wanted to flush it back to zero so it would refill with commonly-used data; so, I disabled the tunable, rebooted the box, and it showed my L2ARC was at zero; I then re-enabled the tunable, and rebooted again and when the system came up; it shows my L2ARC is full.
I thought L2ARC, if persistence was not set, it would be flushed at boot?
I mean at this point I could remove the Cache VDEV and re-add it which should absolutely flush it out, but still, I thought when a system was rebooted w/o Persistence, it would nuke it as part of bringing the pool online?
I have a 2TB NVMe that I have set as my L2ARC.
I had set L2ARC persistence with the tunable vfs.zfs.l2arc.rebuild_enabled = 1 : SYSCTL; and managed to fill it while doing a lot of IO (hindsight I should have removed the Cache VDEV beforehand, but oh well)
I wanted to flush it back to zero so it would refill with commonly-used data; so, I disabled the tunable, rebooted the box, and it showed my L2ARC was at zero; I then re-enabled the tunable, and rebooted again and when the system came up; it shows my L2ARC is full.
I thought L2ARC, if persistence was not set, it would be flushed at boot?
I mean at this point I could remove the Cache VDEV and re-add it which should absolutely flush it out, but still, I thought when a system was rebooted w/o Persistence, it would nuke it as part of bringing the pool online?
