All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14741] New: e2fsck is failing during cronjob build where fail to create .tar image
Date: Mon, 04 Apr 2022 06:25:56 +0000	[thread overview]
Message-ID: <bug-14741-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14741

            Bug ID: 14741
           Summary: e2fsck is failing during cronjob build where fail to
                    create .tar image
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: sujithkumar0903@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

tune2fs 1.42.12 (29-Aug-2014)
tune2fs 1.42.12 (29-Aug-2014)

Please run e2fsck on the filesystem.

Creating journal inode: 
Journal size too big for filesystem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-04-04  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  6:25 bugzilla [this message]
2022-04-04  6:37 ` [Buildroot] [Bug 14741] e2fsck is failing during cronjob build where fail to create .tar image bugzilla
2022-04-04  7:03 ` bugzilla
2022-04-04  7:09 ` bugzilla
2022-04-04  7:25 ` bugzilla
2023-09-11 18:17 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14741-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.