[lustre-discuss] Writing barrier stuck in failed state.

[Sergey Vergun]

openat(AT_FDCWD, "/dev/obd", O_RDWR)    = 3
ioctl(3, _IOC(_IOC_READ|_IOC_WRITE, 0x66, 0x7f, 0x8), 0x7ffea24f1a90) = 0
ioctl(3, _IOC(_IOC_READ|_IOC_WRITE, 0x67, 0x5, 0x8), 0x7ffea24f3da0) = -1
EINVAL (Invalid argument)

Strace show something like it doing both old and new ioctl numbers('g' 5
and 'f' 105) and fail on old one (new added in LU-16634) Should it be like
that?

вт, 22 апр. 2025 г. в 12:04, Sergey Vergun <sewergun at gmail.com>:

> Hello. We have lustre 2.15.4 on Rocky 8.9
> Two MDS with ZFS backend.
> After some time doing snapshots writing barrier stuck in failed state.
>
> Filesystem seems like working but I can't take snapshots anymore.
> barrier_thaw or rescan throw error "Invalid argument" and "-b off" option
> for snapshot_create have no effect. lsnapshot.log say that I call snapshot
> creation with barrier ON even if I say to not use it.
>
> How can I find what caused failed state to prevent that in future and is
> it possible to unlock?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20250707/062f9ec8/attachment.htm>