Hi Piotr,<br><br>Which lustre version is this? Also which version of e2fsprogs are you using?<br>Is the back end disk a software RAID or HW raid? If you can not see any errors on your hardware I would recommend to run fsck few times until it does does not find any problems. I also highly recommend to collect logs from each fsck run in case they are needed for further debugging. If you are not sure that your hardware is OK then you may want to run fsck with -n switch and send output to mailing list.<br>
<br>Best regards,<br><br>Wojciech <br><br><div class="gmail_quote">On 16 June 2011 13:33, Piotr Przybylo <span dir="ltr"><<a href="mailto:piotr_przybylo@polcom.com.pl">piotr_przybylo@polcom.com.pl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<font size="3">We have a problem with lustre, in connection with
this I wanted to ask
you, can you help us ?<br>
We have a unexpect file system error during normal system working.<br>
<i><br>
Jun 13 15:00:30 ossw12 kernel: LDISKFS-fs error (device dm-9): <br>
mb_free_blocks: double-free of inode 82041293's block
346591170(bit 4034
<br>
in group 10577)<br>
Jun 13 15:00:30 ossw12 kernel:<br>
Jun 13 15:00:30 ossw12 kernel: Aborting journal on device dm-9.<br>
Jun 13 15:00:30 ossw12 kernel: Remounting filesystem read-only<br>
Jun 13 15:00:30 ossw12 kernel: LDISKFS-fs error (device dm-9): <br>
mb_free_blocks: <3>LustreError: <br>
4026:0:(fsfilt-ldiskfs.c:280:fsfilt_ldiskfs_start()) error
starting <br>
handle for op 8 (106 credits): rc -30<br>
Jun 13 15:00:30 ossw12 kernel: double-free of inode 82041293's
block <br>
346591171(bit 4035 in group 10577)</i><br>
<br>
<br>
Jun 13 15:06:53 ossw12 kernel: LDISKFS-fs error (device dm-12): <br>
mb_free_blocks: double-free of inode 90143054's block
125314561(bit 9729
<br>
in group 3824)<br>
Jun 13 15:06:53 ossw12 kernel:<br>
Jun 13 15:06:53 ossw12 kernel: Aborting journal on device dm-12.<br>
Jun 13 15:06:53 ossw12 kernel: Remounting filesystem read-only<br>
Jun 13 15:06:53 ossw12 kernel: ldiskfs_abort called.<br>
Jun 13 15:06:53 ossw12 kernel: LDISKFS-fs error (device dm-12): <br>
ldiskfs_journal_start_sb: Detected aborted journal<br>
Jun 13 15:06:53 ossw12 kernel: Remounting filesystem read-only<br>
<br>
<br>
Another try to mount file system:<br>
<i><br>
Jun 13 15:12:24 ossw12 kernel: kjournald starting. Commit
interval
5 <br>
seconds<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS-fs warning (device dm-9):
<br>
ldiskfs_clear_journal_err: Filesystem error recorded from
previous <br>
mount: IO failure<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS-fs warning (device dm-9):
<br>
ldiskfs_clear_journal_err: Marking fs in need of filesystem
check.<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS-fs warning: mounting fs
with <br>
errors, running e2fsck is recommended<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS FS on dm-9, internal
journal<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS-fs: recovery complete.<br>
Jun 13 15:12:24 ossw12 kernel: LDISKFS-fs: mounted filesystem
with <br>
ordered data mode.</i><br>
<br>
<i><br>
Jun 13 15:16:48 ossw12 kernel: kjournald starting. Commit
interval
5 <br>
seconds<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS-fs warning (device
dm-12): <br>
ldiskfs_clear_journal_err: Filesystem error recorded from
previous <br>
mount: IO failure<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS-fs warning (device
dm-12): <br>
ldiskfs_clear_journal_err: Marking fs in need of filesystem
check.<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS-fs warning: mounting fs
with <br>
errors, running e2fsck is recommended<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS FS on dm-12, internal
journal<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS-fs: recovery complete.<br>
Jun 13 15:16:48 ossw12 kernel: LDISKFS-fs: mounted filesystem
with <br>
ordered data mode.</i><br>
<br>
How we can recover or repair data from this devices ?<br>
fsck repair some errors, but then we try mount files system we
have errors:<br>
<i><br>
Jun 13 18:39:17 ossw12 kernel: LDISKFS-fs error (device dm-9):
mb_free_blocks:
double-free of inode 82041293's block 346591170(bit 4034 in
group 10577)<br>
Jun 13 18:39:17 ossw12 kernel:<br>
Jun 13 18:39:17 ossw12 kernel: Aborting journal on device dm-9.<br>
Jun 13 18:39:17 ossw12 kernel: Remounting filesystem read-only<br>
Jun 13 18:39:17 ossw12 kernel: LDISKFS-fs error (device dm-9):
mb_free_blocks:
double-free of inode 82041293's block 346591171(bit 4035 in
group 10577)<br>
Jun 13 18:39:17 ossw12 kernel:<br>
Jun 13 18:39:17 ossw12 kernel: LDISKFS-fs error (device dm-9):
mb_free_blocks:
double-free of inode 82041293's block 346591172(bit 4036 in
group 10577)</i><br>
<br>
Hardware doesnt report any problems.</font>
<pre cols="72">--
Regards
| Piotr Przybylo | Technical Support Engineer | Polcom Sp z o.o. |
| ul. Krakowska 43 | 32-050 Skawina, Poland |
| mobile: +48609539945 | tel: +48 12 652 8682 |
</pre>
</div>
<br>_______________________________________________<br>
Lustre-discuss mailing list<br>
<a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Wojciech Turek<br>