SUSECON
Results 1 to 3 of 3

Thread: why file system became corrupted

Threaded View

  1. why file system became corrupted

    OS: SLES 11 SP 3 + online updates.

    Customer started noticing the following error:
    Jul 22 13:45:30 node1 kernel: [23580.074503] EXT3-fs error (device dm-3): ext3_lookup: deleted inode referenced: 1352479

    and then on 20th Aug, it was noticed 32 errors in b/w 08:47:11 and 08:47:14
    Aug 20 08:47:11 node1 kernel: [2510147.739895] EXT3-fs error (device dm-3): ext3_lookup: deleted inode referenced: 1352539
    .
    .
    .
    Aug 20 08:47:14 node1 kernel: [2510150.315486] EXT3-fs error (device dm-3): ext3_lookup: deleted inode referenced: 1352539

    They also noticed that Application(SAP) using this file system became unfunctional, then a reboot and running the fsck.ext3 was issued to repair the file system.

    Now question here is why it got corrupted ? and what should one do to avoid such errors in future.

    Regards,
    Last edited by sharfuddin; 28-Aug-2015 at 13:31.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •