Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 May 2021 13:43:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        fs@FreeBSD.org
Subject:   [Bug 256205] lseek() with SEEK_HOLE some times wrongly reports holes on ZFS
Message-ID:  <bug-256205-3630-x3CxUAl2CI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-256205-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-256205-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256205

Alan Somers <asomers@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |asomers@FreeBSD.org

--- Comment #5 from Alan Somers <asomers@FreeBSD.org> ---
Let's take a look at the layout of the good vs bad files.  First, do "ls -l=
i"
to get the inode number of the bad file (ved) and the good file (ved.copy).=
=20
Then do "sudo zdb -ddddd <pool>/<dataset> <inode>".  That will show exactly
where ZFS thinks there are holes.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256205-3630-x3CxUAl2CI>