Clovertech

Inode corruption in Cloverleaf filesystem

› Clovertech Forums › Cloverleaf › Inode corruption in Cloverleaf filesystem

Tagged: 

  • Creator
    Topic
  • July 31, 2019 at 12:18 pm #111170
    Bob Schmid
    Participant

      Running CL 6.1.2 AIX 6100-09..are there any known causes of inode corruption within cloverleaf.

      most of the inode errors (command fsck on cloverleaf lv) seem to deal with a pointer to either a smat file or log file (which are cycled regularly >1 time a day)

      What “Could cause ” a bad inode ? and is it detrimental to Cloverleaf?…….
      Is there a recommended triage.

      Its only occurring in the Cloverleaf filesystem……and the orphaned files/bad inodes (found by running an fsck)

      ex inode reported on by fsck is 123455

      Currently doing a find $HCIROOT/* -i 123455, and deleting the file point to.

      but looking for cause, implications and ultimately, fix

       

       

       

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • July 31, 2019 at 2:13 pm #111175
        Bob Schmid
        Participant

          if you run an fsck against the Cloverleaf filesystem…you can see if you too 🙂 have corrupted inodes.  ->   fsck /Cloverleaf     Cloverleaf can be mounted…..its  a readonly run.

        • August 1, 2019 at 5:08 am #111195
          Robert Kersemakers
          Participant

            We have had some ‘bad blocks’ after we went live with CL6.2 earlier this year. No idea if they are related or where the bad blocks came from. We had to do shut down Cloverleaf completely and do a ‘chkdsk’ to mark the blocks as bad.

            Never seen this before since we went to RedHeat.

            Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

          • August 2, 2019 at 9:13 am #111231
            Bob Schmid
            Participant

              ty  Robert

          • Author
            Replies
          Viewing 2 reply threads
          • You must be logged in to reply to this topic.