On Sat, Feb 11, 2012 at 11:47:14AM -0700, Andreas Dilger wrote:
>
> Looks interesting and useful... I wonder if it makes sense to include
> this into e2fsprogs at some point, so that it is available when users
> need it most...
We'll need to talk to the author about that. At the very least it
w
On 2012-02-11, at 11:30 AM, Ted Ts'o wrote:
> On Sat, Feb 11, 2012 at 05:33:30PM +, Rudolf Zran wrote:
>> Hi List!
>>
>> In an offlist reply someone recommended me ext4magic (see
>> http://developer.berlios.de/projects/ext4magic ).
>
> I wasn't familiar with ext4magic, so thanks for recommend
On Sat, Feb 11, 2012 at 05:33:30PM +, Rudolf Zran wrote:
> Hi List!
>
> In an offlist reply someone recommended me ext4magic (see
> http://developer.berlios.de/projects/ext4magic ).
I wasn't familiar with ext4magic, so thanks for recommending it.
After taking a quick look at its wiki page, it
Hi List!
In an offlist reply someone recommended me ext4magic (see
http://developer.berlios.de/projects/ext4magic ).
Like magic it recovered complete directory hierarchies with filenames,
timestamps, even ownership and permissions for more than 300GB of the
deleted data.
I can recommend this to
I, too, very recently lost all the files on a 1000 Gbyte drive,
because of a stupid blunder in attempting to format a USB flash drive.
>From this, I learned two things:
(1) Even a simple listing of the contents of a drive would be
invaluable in attempting to restore the drive from other sources.
On 02/10/2012 06:07 PM, Rudolf Zran wrote:
Hello Bernd!
I have written some tools in the past to recover the file structure of
an over-formated ext3/ext4 device based on directory blocks.
With some tweaks it should be able to assign the file#inode_numbers in
lost+found to a directory structure
On 02/10/2012 10:32 PM, Ted Ts'o wrote:
On Fri, Feb 10, 2012 at 06:36:52PM +, Rudolf Zran wrote:
* "fsck.ext4 -b $SBOK -B 4096 -v -y /dev/loop0" recoveres after a long time.
Filesystem is mountable. Root is empty besides lost+found folder, which
contains about 300GB mostly useless data
On Fri, Feb 10, 2012 at 06:36:52PM +, Rudolf Zran wrote:
> >> * "fsck.ext4 -b $SBOK -B 4096 -v -y /dev/loop0" recoveres after a long
> >> time.
> >> Filesystem is mountable. Root is empty besides lost+found folder, which
> >> contains about 300GB mostly useless data: Millions of files with
Hello Ted!
>> I recently damaged an ext4 partition by accident
[...]
>> Maybe somebody knows a good method to just "repair" the
>> ext4-structure from the remaining part of the partition?
>
> Have you tried just simply running e2fsck, specifying an alternate superblock?
Yes of course I tried,
On Feb 9, 2012, at 11:29 AM, Rudolf Zran wrote:
> Hi everybody!
>
> I recently damaged an ext4 partition by accident (mistakenly forced
> a RAID sync with another partition onto it, which I realized after
> about 3% completion). As a result the beginning of the ext4 partition
> seems to be overw
Hello Bernd!
> I have written some tools in the past to recover the file structure of
> an over-formated ext3/ext4 device based on directory blocks.
> With some tweaks it should be able to assign the file#inode_numbers in
> lost+found to a directory structure.
> Problem is that I'm rather busy
On 02/09/2012 10:22 PM, Rudolf Zran wrote:
Hello Andreas!
[ext4 partition overwritten with garbage at the beginning]
* photorec from the testdisk package recoveres, luckily!, about 500GB of
data. Though the content seems to be pretty reasonable, no filenames
are recovered, since ph
On Thu, 09 Feb 2012 16:29:53 +, Rudolf Zran wrote:
> Hi everybody!
>
> I recently damaged an ext4 partition by accident (mistakenly forced a
> RAID sync with another partition onto it, which I realized after about
> 3% completion). As a result the beginning of the ext4 partition seems to
> be
Hello Andreas!
[ext4 partition overwritten with garbage at the beginning]
>> * photorec from the testdisk package recoveres, luckily!, about 500GB of
>> data. Though the content seems to be pretty reasonable, no filenames
>> are recovered, since photorec operates without using filesystem
On 2012-02-09, at 9:29 AM, Rudolf Zran wrote:
> I recently damaged an ext4 partition by accident (mistakenly forced
> a RAID sync with another partition onto it, which I realized after
> about 3% completion). As a result the beginning of the ext4 partition
> seems to be overwritten with garbage and
15 matches
Mail list logo
