linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 210795] fsck.f2fs - 1.14.0 - error when not /dev/vgXX/lvYYY path provided - [ASSERT] (init_sb_info:1017) !strcmp((char *)sb->devs[i].path, (char *)c.devices[i].path)
Date: Fri, 29 Sep 2023 14:51:07 +0000	[thread overview]
Message-ID: <bug-210795-202145-2ycWO6nyFH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210795-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210795

Tomas Thiemel (thiemel@centrum.cz) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |DOCUMENTED

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2023-09-29 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  5:28 [f2fs-dev] [Bug 210795] New: fsck.f2fs - 1.14.0 - error when not /dev/vgXX/lvYYY path provided - [ASSERT] (init_sb_info:1017) !strcmp((char *)sb->devs[i].path, (char *)c.devices[i].path) bugzilla-daemon
2020-12-21  1:18 ` [f2fs-dev] [Bug 210795] " bugzilla-daemon
2023-09-29 14:51 ` bugzilla-daemon [this message]

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-210795-202145-2ycWO6nyFH@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).