Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-3991

mkfs.lustre failed to copy pool name

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Blocker
    • None
    • Lustre 2.5.0
    • 3
    • 10669

    Description

      When running mkfs.lustre on a new file, mkfs.lustre can't create the file automatically, but reports error 2 "No such file or directory".

      This bug is introduced by LU-3682. I will fix it.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-3682 "tunefs.lustre --erase_params" corrupts running MGS when run against device node symlink

          • Critical - Crashes, loss of data, severe memory leak.
          • Reopened

          Activity

            [LU-3991] mkfs.lustre failed to copy pool name
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-3682 [ LU-3682 ]
            pjones Peter Jones made changes -
            Fix Version/s Original: Lustre 2.5.0 [ 10295 ]
            pjones Peter Jones made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            pjones Peter Jones added a comment -

            Should no longer exist now LU-3682 has been reverted

            pjones Peter Jones added a comment - Should no longer exist now LU-3682 has been reverted
            emoly.liu Emoly Liu added a comment -

            Resubmit the patch. Please have a look.

            emoly.liu Emoly Liu added a comment - Resubmit the patch. Please have a look.
            utopiabound Nathaniel Clark made changes -
            Labels Original: HB zfs New: HB revzfs zfs
            jlevi Jodi Levi (Inactive) made changes -
            Labels Original: zfs New: HB zfs
            Priority Original: Minor [ 4 ] New: Blocker [ 1 ]
            adilger Andreas Dilger made changes -
            Summary Original: mkfs.lustre failed to create a new file automatically New: mkfs.lustre failed to copy pool name
            adilger Andreas Dilger made changes -
            Labels New: zfs
            adilger Andreas Dilger added a comment -

            I don't think that creating loopback files automatically is a good idea. In the normal use case (instead if during testing) any typo or error in the device name will result in a loopback file being created instead if returning a useful error to the user. For example, if someone accidentally runs "mkfs.lustre /dev/sfa" instead of "sda" this will result in a loopback file being created in /dev that will initially work, but will be very slow and will later fail when the root Filesystem runs pit of space.

            I would rather that testers/scripts make sure that the loopback file it created first, and allow mkfs.lustre to return an error if this us not done correctly.

            Please resubmit the patch with just the other bug fixes.

            adilger Andreas Dilger added a comment - I don't think that creating loopback files automatically is a good idea. In the normal use case (instead if during testing) any typo or error in the device name will result in a loopback file being created instead if returning a useful error to the user. For example, if someone accidentally runs "mkfs.lustre /dev/sfa" instead of "sda" this will result in a loopback file being created in /dev that will initially work, but will be very slow and will later fail when the root Filesystem runs pit of space. I would rather that testers/scripts make sure that the loopback file it created first, and allow mkfs.lustre to return an error if this us not done correctly. Please resubmit the patch with just the other bug fixes.

            People

              emoly.liu Emoly Liu
              emoly.liu Emoly Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: