<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
zfs is 0.6.4.2<br>
<br>
bob<br>
<br>
<div class="moz-cite-prefix">On 3/12/2016 1:44 AM, Alexander I
Kulyavtsev wrote:<br>
</div>
<blockquote cite="mid:0A07901D-1222-4219-B20E-75FF87747088@fnal.gov"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div><br>
</div>
<div>You lost one "file" only:</div>
<div>
<blockquote type="cite"><font color="#000000"><span
style="background-color: rgba(255, 255, 255, 0);">0x2c90f</span></font></blockquote>
<div><br>
</div>
I wold take zfs snapshot on ost, mount it as zfs and try to find
lustre FID of the file.<br>
<br>
If that does not work, I guess zdb with high verbosity level can
help to pinpoint broken zfs object, like in</div>
<div>"<span style="background-color: rgba(255, 255, 255, 0);
font-size: medium;">zdb: Examining ZFS At Point-Blank Range,</span>"
and see what it is (plain zfs file or else).</div>
<div><br>
</div>
<div>Knowing zfs version can be helpful.</div>
<div><br>
<div>Alex</div>
</div>
<div><br>
On Mar 11, 2016, at 7:19 PM, Bob Ball <<a
moz-do-not-send="true" href="mailto:ball@umich.edu"><a class="moz-txt-link-abbreviated" href="mailto:ball@umich.edu">ball@umich.edu</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite"><span>errors: Permanent errors have been
detected in the following files:</span><br>
<span></span><br>
<span> ost-007/ost0030:<0x2c90f></span></blockquote>
</blockquote>
<br>
</body>
</html>