Yes, it sure sounds like I'm going to have to resurrect my test system
and upgrade to the 2.9 release. There just does not seem to be a way
around this.
bob
On 2/18/2017 12:40 AM, Dilger, Andreas wrote:
Just a note - Lustre 2.7.58 is a random weekly development tag (like anything
between
Just a note - Lustre 2.7.58 is a random weekly development tag (like anything
between .50 and .90), so you would be better off to update to the latest
release (e.g. 2.8.0 or 2.9.0), which will have had much more testing.
Likewise, ZFS 0.6.4.x is quite old and many fixes have gone into ZFS
No luck, removed all files, destroyed the zpool, replaced all physical
disks, and upon re-creation, the zfs PANIC will strike once the number
of clients attempting accesses exceeds something just under 200.
Other OST on this OSS do not suffer from this.
Suggestions, anyone? At this point, it
OK, so, I tried some new system mounts today, and each time the new
client attempts to mount, the zfs PANIC throws. This from 2 separate
client machines. It seems clear from the responsiveness problem last
week that it is impacting a single OST. After it happens, I power cycle
the OSS
Well, I find this odd, to say the least. All of this below was from
yesterday, and persisted through a couple of reboots. Today, shortly
after I sent this, I found all the disks idle, but this one OST out of 6
totally unresponsive, so I power cycled the system, and it came up just
fine. No
Hi,
I am getting this message
PANIC: zfs: accessing past end of object 29/7 (size=33792 access=33792+128)
The affected OST seems to reject new mounts from clients now, and the
lctl dl count of connections to the obdfilter process increases, but
does not seem to decrease?
This is Lustre
