From: Viliam Lejcik <Viliam.Lejcik@kistler.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: RE: e2fsprogs: setting UUID with tune2fs corrupts an ext4 fs image
Date: Thu, 5 Dec 2019 16:51:55 +0000 [thread overview]
Message-ID: <a7dc8a59e6be4974a800b87d633807e8@kistler.com> (raw)
Hi Theodore,
Thank you for quick response. You can download the sample image here:
https://smartfile.kistler.com/link/Oggq7B33BaI/
It was slightly modified (I deleted some proprietary stuff), as it is difficult to build a sample image which leads to this problem. So you may find the issue on another inode, but if you run the commands as stated in the report, you'll be able to reproduce the issue, for sure.
BR,
Vilo
Confidentiality Notice: This e-mail is privileged and confidential and for the use of the addressee only. Should you have received this e-mail in error please notify us by replying directly to the sender or by sending a message to info@kistler.com. Unauthorised dissemination, disclosure or copying of the contents of this e-mail, or any similar action, is prohibited.
-----Original Message-----
From: Theodore Y. Ts'o <tytso@mit.edu>
Sent: Thursday, 5. December 2019 16:48
To: Lejcik Viliam <Viliam.Lejcik@kistler.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs: setting UUID with tune2fs corrupts an ext4 fs image
On Thu, Dec 05, 2019 at 12:36:35PM +0000, Viliam Lejcik wrote:
>
> This behavior can be reproduced on an ext4 fs image, so there's no need to run it on the device.
Where can we download or otherwise obtain the image where you are seeing the problem?
Thanks,
- Ted
next reply other threads:[~2019-12-05 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 16:51 Viliam Lejcik [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 12:36 e2fsprogs: setting UUID with tune2fs corrupts an ext4 fs image Viliam Lejcik
2019-12-05 15:48 ` Theodore Y. Ts'o
2019-12-06 3:51 ` Theodore Y. Ts'o
2019-12-09 14:44 ` Viliam Lejcik
2019-12-05 9:20 Viliam Lejcik
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=a7dc8a59e6be4974a800b87d633807e8@kistler.com \
--to=viliam.lejcik@kistler.com \
--cc=linux-ext4@vger.kernel.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 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).