Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13635

Backup warnings when performing tar.gz

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: periodicbackup-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.459, Running on Ubuntu Linux.
      Periodic Backup Version 1.1
    • Similar Issues:

      Description

      The jenkins log is filled with lines like the following (whenever it goes to do a backup):
      [INFO] Building tar: ...
      ...
      "[WARNING] Entry: jobs/.../.../.../... longer than 100 characters"
      ...

      The backups appear to be completing still, but am not 100% sure if the tar files are corrupt or not.

      Doing my own minor research indicates that adding the '-E' flag will allow for longer filenames, so perhaps this is something that should be added to the plugin?

        Attachments

          Activity

          Hide
          johno Johno Crawford added a comment - - edited

          For clarity sake, the new limit is now 256 characters.

          Show
          johno Johno Crawford added a comment - - edited For clarity sake, the new limit is now 256 characters.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Johno Crawford
          Path:
          src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java
          http://jenkins-ci.org/commit/periodicbackup-plugin/4bf5a1269b2ba39f6a1eb6fefc57f6230aea9c48
          Log:
          Merge pull request #5 from johnou/long-filenames

          JENKINS-13635: Backup warnings when performing tar.gz

          Compare: https://github.com/jenkinsci/periodicbackup-plugin/compare/7a3bfc8e44dc...4bf5a1269b2b

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java http://jenkins-ci.org/commit/periodicbackup-plugin/4bf5a1269b2ba39f6a1eb6fefc57f6230aea9c48 Log: Merge pull request #5 from johnou/long-filenames JENKINS-13635 : Backup warnings when performing tar.gz Compare: https://github.com/jenkinsci/periodicbackup-plugin/compare/7a3bfc8e44dc...4bf5a1269b2b
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Johno Crawford
          Path:
          src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java
          http://jenkins-ci.org/commit/periodicbackup-plugin/8b1d53035609c11acee5e8512104ea9c08810efb
          Log:
          JENKINS-13635: Backup warnings when performing tar.gz

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java http://jenkins-ci.org/commit/periodicbackup-plugin/8b1d53035609c11acee5e8512104ea9c08810efb Log: JENKINS-13635 : Backup warnings when performing tar.gz
          Hide
          johno Johno Crawford added a comment -

          Fixed next build, archiver now creates GNU tars.

          Show
          johno Johno Crawford added a comment - Fixed next build, archiver now creates GNU tars.
          Hide
          johno Johno Crawford added a comment -

          http://www.delorie.com/gnu/docs/tar/tar_114.html

          GNU tar was based on an early draft of the POSIX 1003.1 ustar standard. GNU extensions to tar, such as the support for file names longer than 100 characters, use portions of the tar header record which were specified in that POSIX draft as unused. Subsequent changes in POSIX have allocated the same parts of the header record for other purposes. As a result, GNU tar is incompatible with the current POSIX spec, and with tar programs that follow it.

          POSIX mandates that, when a file name cannot fit within 100 to 256 characters (the variance comes from the fact a / is ideally needed as the 156'th character), or a link name cannot fit within 100 characters, a warning should be issued and the file not be stored. Unless some --posix option is given (or POSIXLY_CORRECT is set), I suspect that GNU tar should disobey this specification, and automatically switch to using GNU extensions to overcome file name or link name length limitations.

          Show
          johno Johno Crawford added a comment - http://www.delorie.com/gnu/docs/tar/tar_114.html GNU tar was based on an early draft of the POSIX 1003.1 ustar standard. GNU extensions to tar, such as the support for file names longer than 100 characters, use portions of the tar header record which were specified in that POSIX draft as unused. Subsequent changes in POSIX have allocated the same parts of the header record for other purposes. As a result, GNU tar is incompatible with the current POSIX spec, and with tar programs that follow it. POSIX mandates that, when a file name cannot fit within 100 to 256 characters (the variance comes from the fact a / is ideally needed as the 156'th character), or a link name cannot fit within 100 characters, a warning should be issued and the file not be stored. Unless some --posix option is given (or POSIXLY_CORRECT is set), I suspect that GNU tar should disobey this specification, and automatically switch to using GNU extensions to overcome file name or link name length limitations.
          Hide
          johno Johno Crawford added a comment -

          duh, Ubuntu Linux.

          Show
          johno Johno Crawford added a comment - duh, Ubuntu Linux.
          Hide
          johno Johno Crawford added a comment -

          What OS is your platform?

          Show
          johno Johno Crawford added a comment - What OS is your platform?

            People

            Assignee:
            johno Johno Crawford
            Reporter:
            casualt A K
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: