MIME-Version: 1.0
References: <CABxFBzGv9vJsw_f9FJmJvQ2GZaz1NnVkK9a6y6CT58bv3mZj2A@mail.gmail.com>
 <CABxFBzE-kOtf3hO26RH1S7CmM+AeB6qso8OQBDOysH1L9rmjnQ@mail.gmail.com> <093e8c89-79f7-e207-6cb5-d66dadab60c2@thelounge.net>
In-Reply-To: <093e8c89-79f7-e207-6cb5-d66dadab60c2@thelounge.net>
From:   Andrea Lo Pumo <alopumo@movia.biz>
Date:   Thu, 11 Apr 2019 11:45:46 +0200
Message-ID: <CABxFBzGK9qSny7PdFOxpjK2evr8xZ5xCECRkcKCou1R-uyVu+g@mail.gmail.com>
Subject: Re: Run mkfs.ext4 on an already existing ext4 filesystem. Seeking
 professional help or programming hints for the recovery.
Cc:     linux-ext4@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
To:     unlisted-recipients:; (no To-header on input)
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

Il giorno gio 11 apr 2019 alle ore 11:42 Reindl Harald
<h.reindl@thelounge.net> ha scritto:
>
> Am 11.04.19 um 11:37 schrieb Andrea Lo Pumo:
> > On /dev/sda1(*) there was an ext4 file system with a lot of large
> > files. Now, by mistake, mkfs.ext4 has been run on /dev/sda1. The
> > result is that now /dev/sda1 is "empty": mounting it shows no files.
> >
> > Note *: actually, it is /dev/mapper/secure_storage, an encrypted
> > volume opened with LUKS: cryptsetup luksOpen /dev/sda1 secure_storage
>
> no
>
> you said you had a LUKS volume on /dev/sda1 which means by directly
> create a fs on /dev/sda1 you have overwritten parts of the encryption
> layer *and* at the same time the filesystem *on top* of it

Sorry, I explained it badly. The commands were:

  cryptsetup luksOpen /dev/sda1 secure_storage
  mkfs.ext4 /dev/mapper/secure_storage