Re: fsck -C -p: NO WRITE ACCESS
- In reply to: Andriy Gapon : "Re: fsck -C -p: NO WRITE ACCESS"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 10 Feb 2022 07:31:34 UTC
On 10/02/2022 09:05, Andriy Gapon wrote: > Interesting... we have this sequence of opens: O_RDONLY, O_WRONLY, O_RDONLY, > O_WRONLY. And for some reason the second O_WRONLY open fails. > Perhaps something gets confused on the GEOM / GELI side. It looks like closing after the first O_WRONLY open triggers the GEOM re-taste. When the second O_WRONLY is attempted there is a chance (which is very high on my system) that something has the GEOM provider opened with read and exclusive bits. It's the exclusive bit that causes the open to fail. Looks like it's g_label_taste. Not sure if something recently changed in that area or if I've just got much "luckier". -- Andriy Gapon