Greyhole behavior with full pool but room in LZ
-
- Posts: 49
- Joined: Fri Oct 12, 2012 7:32 pm
Greyhole behavior with full pool but room in LZ
So my question is exactly what it say in the subject, what could I expect to happen if Greyhole finds itself in a situation where the LZ has more data than can be transferred to the pool? It's not an immediate issue, but I'm hoping that it can handle it reasonably gracefully...
Re: Greyhole behavior with full pool but room in LZ
I would imagine you just get a disk full error in windows when trying to transfer something that is larger than available, because samba/cifs reports the size of the pool, not the landing zone. The LZ is abstracted to the clients. It's just there to facilitate greyhole moving files into the pool.
Think of it like the LZ as the invisible diving board. Windows sees the pool, and the files going into the pool, and knows when the pool won't fit another item, even if it could walk the diving board.
Think of it like the LZ as the invisible diving board. Windows sees the pool, and the files going into the pool, and knows when the pool won't fit another item, even if it could walk the diving board.
SgtFoo
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch
Who is online
Users browsing this forum: No registered users and 24 guests