how to perform xfs_repair on disk that is actually UUID

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












we have redhat machines version 6.x



we want to fix the file-system on one of our disks



UUID=198s5364-a29c-429e-b16d-e772acd /data_SA xfs rw,noatime,inode64,allocsize=16m 1 2


but disk is UUID



so dose the following syntax is right ?



xfs_repair UUID=198s5364-a29c-429e-b16d-e772acd 


FROM MAN PAGE



SYNOPSIS
xfs_repair [ -dfLnPv ] [ -m maxmem ] [ -c subopt=value ] [ -o subopt[=value] ] [ -t interval ] [ -l logdev ] [ -r rtdev ] device
xfs_repair -V






share|improve this question

























    up vote
    1
    down vote

    favorite












    we have redhat machines version 6.x



    we want to fix the file-system on one of our disks



    UUID=198s5364-a29c-429e-b16d-e772acd /data_SA xfs rw,noatime,inode64,allocsize=16m 1 2


    but disk is UUID



    so dose the following syntax is right ?



    xfs_repair UUID=198s5364-a29c-429e-b16d-e772acd 


    FROM MAN PAGE



    SYNOPSIS
    xfs_repair [ -dfLnPv ] [ -m maxmem ] [ -c subopt=value ] [ -o subopt[=value] ] [ -t interval ] [ -l logdev ] [ -r rtdev ] device
    xfs_repair -V






    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      we have redhat machines version 6.x



      we want to fix the file-system on one of our disks



      UUID=198s5364-a29c-429e-b16d-e772acd /data_SA xfs rw,noatime,inode64,allocsize=16m 1 2


      but disk is UUID



      so dose the following syntax is right ?



      xfs_repair UUID=198s5364-a29c-429e-b16d-e772acd 


      FROM MAN PAGE



      SYNOPSIS
      xfs_repair [ -dfLnPv ] [ -m maxmem ] [ -c subopt=value ] [ -o subopt[=value] ] [ -t interval ] [ -l logdev ] [ -r rtdev ] device
      xfs_repair -V






      share|improve this question













      we have redhat machines version 6.x



      we want to fix the file-system on one of our disks



      UUID=198s5364-a29c-429e-b16d-e772acd /data_SA xfs rw,noatime,inode64,allocsize=16m 1 2


      but disk is UUID



      so dose the following syntax is right ?



      xfs_repair UUID=198s5364-a29c-429e-b16d-e772acd 


      FROM MAN PAGE



      SYNOPSIS
      xfs_repair [ -dfLnPv ] [ -m maxmem ] [ -c subopt=value ] [ -o subopt[=value] ] [ -t interval ] [ -l logdev ] [ -r rtdev ] device
      xfs_repair -V








      share|improve this question












      share|improve this question




      share|improve this question








      edited May 2 at 16:03









      Jeff Schaller

      31.1k846105




      31.1k846105









      asked May 2 at 13:37









      yael

      1,9301144




      1,9301144




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          9
          down vote



          accepted










          You should find your device UUID in /dev/disk/by-uuid:



          xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd





          share|improve this answer





















          • well done - excellent answer
            – yael
            May 2 at 14:31

















          up vote
          6
          down vote













          There is findfs to translate UUID to device names.



          # findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964
          /dev/mapper/SSD-archlinux


          So you can use that to provide arguments that expect device names:



          # echo file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
          file -s /dev/mapper/SSD-archlinux

          # file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
          /dev/mapper/SSD-archlinux: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

          # xfs_repair $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
          Phase 1 - find and verify superblock...
          Phase 2 - using internal log
          - zero log...
          - scan filesystem freespace and inode maps...
          - found root inode chunk
          Phase 3 - for each AG...
          - scan and clear agi unlinked lists...
          - process known inodes and perform inode discovery...
          - agno = 0
          - agno = 1
          - agno = 2
          - agno = 3
          - process newly discovered inodes...
          Phase 4 - check for duplicate blocks...
          - setting up duplicate extent list...
          - check for inodes claiming duplicate blocks...
          - agno = 0
          - agno = 1
          - agno = 2
          - agno = 3
          Phase 5 - rebuild AG headers and trees...
          - reset superblock...
          Phase 6 - check inode connectivity...
          - resetting contents of realtime bitmap and summary inodes
          - traversing filesystem ...
          - traversal finished ...
          - moving disconnected inodes to lost+found ...
          Phase 7 - verify and correct link counts...
          done





          share|improve this answer





















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441323%2fhow-to-perform-xfs-repair-on-disk-that-is-actually-uuid%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            9
            down vote



            accepted










            You should find your device UUID in /dev/disk/by-uuid:



            xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd





            share|improve this answer





















            • well done - excellent answer
              – yael
              May 2 at 14:31














            up vote
            9
            down vote



            accepted










            You should find your device UUID in /dev/disk/by-uuid:



            xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd





            share|improve this answer





















            • well done - excellent answer
              – yael
              May 2 at 14:31












            up vote
            9
            down vote



            accepted







            up vote
            9
            down vote



            accepted






            You should find your device UUID in /dev/disk/by-uuid:



            xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd





            share|improve this answer













            You should find your device UUID in /dev/disk/by-uuid:



            xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd






            share|improve this answer













            share|improve this answer



            share|improve this answer











            answered May 2 at 13:50









            Stephen Kitt

            140k22302363




            140k22302363











            • well done - excellent answer
              – yael
              May 2 at 14:31
















            • well done - excellent answer
              – yael
              May 2 at 14:31















            well done - excellent answer
            – yael
            May 2 at 14:31




            well done - excellent answer
            – yael
            May 2 at 14:31












            up vote
            6
            down vote













            There is findfs to translate UUID to device names.



            # findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964
            /dev/mapper/SSD-archlinux


            So you can use that to provide arguments that expect device names:



            # echo file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
            file -s /dev/mapper/SSD-archlinux

            # file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
            /dev/mapper/SSD-archlinux: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

            # xfs_repair $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
            Phase 1 - find and verify superblock...
            Phase 2 - using internal log
            - zero log...
            - scan filesystem freespace and inode maps...
            - found root inode chunk
            Phase 3 - for each AG...
            - scan and clear agi unlinked lists...
            - process known inodes and perform inode discovery...
            - agno = 0
            - agno = 1
            - agno = 2
            - agno = 3
            - process newly discovered inodes...
            Phase 4 - check for duplicate blocks...
            - setting up duplicate extent list...
            - check for inodes claiming duplicate blocks...
            - agno = 0
            - agno = 1
            - agno = 2
            - agno = 3
            Phase 5 - rebuild AG headers and trees...
            - reset superblock...
            Phase 6 - check inode connectivity...
            - resetting contents of realtime bitmap and summary inodes
            - traversing filesystem ...
            - traversal finished ...
            - moving disconnected inodes to lost+found ...
            Phase 7 - verify and correct link counts...
            done





            share|improve this answer

























              up vote
              6
              down vote













              There is findfs to translate UUID to device names.



              # findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964
              /dev/mapper/SSD-archlinux


              So you can use that to provide arguments that expect device names:



              # echo file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
              file -s /dev/mapper/SSD-archlinux

              # file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
              /dev/mapper/SSD-archlinux: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

              # xfs_repair $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
              Phase 1 - find and verify superblock...
              Phase 2 - using internal log
              - zero log...
              - scan filesystem freespace and inode maps...
              - found root inode chunk
              Phase 3 - for each AG...
              - scan and clear agi unlinked lists...
              - process known inodes and perform inode discovery...
              - agno = 0
              - agno = 1
              - agno = 2
              - agno = 3
              - process newly discovered inodes...
              Phase 4 - check for duplicate blocks...
              - setting up duplicate extent list...
              - check for inodes claiming duplicate blocks...
              - agno = 0
              - agno = 1
              - agno = 2
              - agno = 3
              Phase 5 - rebuild AG headers and trees...
              - reset superblock...
              Phase 6 - check inode connectivity...
              - resetting contents of realtime bitmap and summary inodes
              - traversing filesystem ...
              - traversal finished ...
              - moving disconnected inodes to lost+found ...
              Phase 7 - verify and correct link counts...
              done





              share|improve this answer























                up vote
                6
                down vote










                up vote
                6
                down vote









                There is findfs to translate UUID to device names.



                # findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964
                /dev/mapper/SSD-archlinux


                So you can use that to provide arguments that expect device names:



                # echo file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                file -s /dev/mapper/SSD-archlinux

                # file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                /dev/mapper/SSD-archlinux: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

                # xfs_repair $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                Phase 1 - find and verify superblock...
                Phase 2 - using internal log
                - zero log...
                - scan filesystem freespace and inode maps...
                - found root inode chunk
                Phase 3 - for each AG...
                - scan and clear agi unlinked lists...
                - process known inodes and perform inode discovery...
                - agno = 0
                - agno = 1
                - agno = 2
                - agno = 3
                - process newly discovered inodes...
                Phase 4 - check for duplicate blocks...
                - setting up duplicate extent list...
                - check for inodes claiming duplicate blocks...
                - agno = 0
                - agno = 1
                - agno = 2
                - agno = 3
                Phase 5 - rebuild AG headers and trees...
                - reset superblock...
                Phase 6 - check inode connectivity...
                - resetting contents of realtime bitmap and summary inodes
                - traversing filesystem ...
                - traversal finished ...
                - moving disconnected inodes to lost+found ...
                Phase 7 - verify and correct link counts...
                done





                share|improve this answer













                There is findfs to translate UUID to device names.



                # findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964
                /dev/mapper/SSD-archlinux


                So you can use that to provide arguments that expect device names:



                # echo file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                file -s /dev/mapper/SSD-archlinux

                # file -s $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                /dev/mapper/SSD-archlinux: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

                # xfs_repair $(findfs UUID=01d91a31-d25c-48ea-a10f-6166ce0f5964)
                Phase 1 - find and verify superblock...
                Phase 2 - using internal log
                - zero log...
                - scan filesystem freespace and inode maps...
                - found root inode chunk
                Phase 3 - for each AG...
                - scan and clear agi unlinked lists...
                - process known inodes and perform inode discovery...
                - agno = 0
                - agno = 1
                - agno = 2
                - agno = 3
                - process newly discovered inodes...
                Phase 4 - check for duplicate blocks...
                - setting up duplicate extent list...
                - check for inodes claiming duplicate blocks...
                - agno = 0
                - agno = 1
                - agno = 2
                - agno = 3
                Phase 5 - rebuild AG headers and trees...
                - reset superblock...
                Phase 6 - check inode connectivity...
                - resetting contents of realtime bitmap and summary inodes
                - traversing filesystem ...
                - traversal finished ...
                - moving disconnected inodes to lost+found ...
                Phase 7 - verify and correct link counts...
                done






                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered May 2 at 13:49









                frostschutz

                24.3k14673




                24.3k14673






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441323%2fhow-to-perform-xfs-repair-on-disk-that-is-actually-uuid%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay