From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 78151] e2image -I does not work on ext4?
Date: Tue, 17 Jun 2014 14:54:54 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: linux-ext4@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:42848 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S933239AbaFQOy4 (ORCPT );
Tue, 17 Jun 2014 10:54:56 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id AADDC202D1
for ; Tue, 17 Jun 2014 14:54:55 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id D7292202F2
for ; Tue, 17 Jun 2014 14:54:54 +0000 (UTC)
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=78151
--- Comment #4 from Theodore Tso ---
The simplest and easist thing if this is what you are trying to do is to store
the inode number along with the md5 checksum in your offline database. Now if
things go really go really bad, you can do this to recover files:
debugfs -id /dev/sda1 /u1/sda1.e2i
debugfs: dump <12345> filename-for-inode-12345
--
You are receiving this mail because:
You are watching the assignee of the bug.