On 09/21/2014 04:14 PM, jd1008 wrote:
So, an ext3fs' superblock, starts at 1K bytes from start of partition, extends
only 1K bytes?
Is this true no matter what block size was chosen for the creation of the FS?
I have been looking for a schematic block diagram layout of the ext[2,3,4]
filesystems
On 09/20/2014 09:41 PM, Robert Nichols wrote:
On 09/20/2014 08:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it unless they know the intrinsics
of the FS s
On 09/21/2014 08:58 AM, Robert Nichols wrote:
On 09/20/2014 10:50 PM, jd1008 wrote:
On 09/20/2014 09:41 PM, Robert Nichols wrote:
On 09/20/2014 08:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using th
On 09/21/2014 03:18 AM, Tom H wrote:
On Sat, Sep 20, 2014 at 9:41 PM, Joe Zeff wrote:
On 09/20/2014 06:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it u
On 09/20/2014 10:50 PM, jd1008 wrote:
On 09/20/2014 09:41 PM, Robert Nichols wrote:
On 09/20/2014 08:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it unle
On Sat, Sep 20, 2014 at 9:41 PM, Joe Zeff wrote:
> On 09/20/2014 06:30 PM, jd1008 wrote:
>>
>> / posted it to the ext3 maling list (turns out they also know ext4)
>> and they admitted about undocumented effects of using the -S
>> option, and that one must NEVER use it unless they know the intrinsi
On 09/20/2014 09:41 PM, Robert Nichols wrote:
On 09/20/2014 08:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it unless they know the intrinsics
of the FS s
On 09/20/2014 08:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it unless they know the intrinsics
of the FS so well, that the user knows exactly what effects
On 09/20/2014 06:30 PM, jd1008 wrote:
/ posted it to the ext3 maling list (turns out they also know ext4)
and they admitted about undocumented effects of using the -S
option, and that one must NEVER use it unless they know the intrinsics
of the FS so well, that the user knows exactly what effects
On 09/20/2014 07:15 PM, Robert Nichols wrote:
On 09/19/2014 08:16 PM, Chris Murphy wrote:
On Sep 19, 2014, at 11:49 AM, jd1008 wrote:
On 09/19/2014 08:39 AM, Robert Nichols wrote:
On 09/18/2014 10:57 PM, jd1008 wrote:
I ran mkfs.ext3 -S /dev/sdc7
then ran fsck.ext3 -y /dev/sdc7
it blew
On 09/19/2014 08:16 PM, Chris Murphy wrote:
On Sep 19, 2014, at 11:49 AM, jd1008 wrote:
On 09/19/2014 08:39 AM, Robert Nichols wrote:
On 09/18/2014 10:57 PM, jd1008 wrote:
I ran mkfs.ext3 -S /dev/sdc7
then ran fsck.ext3 -y /dev/sdc7
it blew away EVERYTHING :)
Back to square one and re-dd
On Sep 19, 2014, at 11:49 AM, jd1008 wrote:
>
> On 09/19/2014 08:39 AM, Robert Nichols wrote:
>> On 09/18/2014 10:57 PM, jd1008 wrote:
>>> I ran mkfs.ext3 -S /dev/sdc7
>>> then ran fsck.ext3 -y /dev/sdc7
>>> it blew away EVERYTHING :)
>>>
>>> Back to square one and re-dd original to test driv
On 09/19/2014 08:39 AM, Robert Nichols wrote:
On 09/18/2014 10:57 PM, jd1008 wrote:
I ran mkfs.ext3 -S /dev/sdc7
then ran fsck.ext3 -y /dev/sdc7
it blew away EVERYTHING :)
Back to square one and re-dd original to test drive
and start over.
Ouch! That _used_ to work. Trying it just now, "m
On 09/18/2014 10:57 PM, jd1008 wrote:
I ran mkfs.ext3 -S /dev/sdc7
then ran fsck.ext3 -y /dev/sdc7
it blew away EVERYTHING :)
Back to square one and re-dd original to test drive
and start over.
Ouch! That _used_ to work. Trying it just now, "mke3fs -S" seems
to clear a substantial portion o
On 09/18/2014 07:01 PM, Robert Nichols wrote:
On 09/18/2014 12:37 PM, jd1008 wrote:
Is there any other tool that can extract files from a partition that
seems to have corrupted superblocks?
I tried dumpe2fs, and fsck -b
to no avail. Tried all available block numbers that are listed
when origin
On 09/18/2014 12:57 PM, Rick Stevens wrote:
On 09/18/2014 11:45 AM, jd1008 issued this missive:
I have been searching for ext2/3 design docs to see where the on-disk
superblock is located relative to starting sector of the partition,
and how
many bytes it occucpies.
I was also looking for t
On 09/18/2014 07:01 PM, Robert Nichols wrote:
On 09/18/2014 12:37 PM, jd1008 wrote:
Is there any other tool that can extract files from a partition that
seems to have corrupted superblocks?
I tried dumpe2fs, and fsck -b
to no avail. Tried all available block numbers that are listed
when origin
On 09/18/2014 12:37 PM, jd1008 wrote:
Is there any other tool that can extract files from a partition that
seems to have corrupted superblocks?
I tried dumpe2fs, and fsck -b
to no avail. Tried all available block numbers that are listed
when original mkfs was done, and it's output was saved.
No
On 09/18/2014 11:42 AM, Nathan Schwarz wrote:
Unmount the partition, `debugfs $partition` and then `extract
$fileOnDamagedFilesystem $targetFileOnExternalFilesystem`. That should
do it - but you should check the man-page since I can't recall if it was
exactly that.
- Nathan
Well, I tried debu
On Thu, Sep 18, 2014 at 06:44:09PM -0400, Tom Horsley wrote:
> One other thing I've seen work: Put the disk in the freezer for
> a while.
I have to comment--only do this if the data on the disk is NOT very
important to you, if you must do it. If it _is_ important, give the
disk to someone like G
On Fri, 19 Sep 2014 00:39:38 +0200 (CEST)
Francisco J. Tsao Santin wrote:
> And you have a last chance with data carving methods (i.e. Foremost or
> Testdisk/Photorec)
One other thing I've seen work: Put the disk in the freezer for
a while. Sometimes it works better cold and you have a few minut
On Thu, 18 Sep 2014, jd1008 wrote:
> Is there any other tool that can extract files from a partition that
> seems to have corrupted superblocks?
> I tried dumpe2fs, and fsck -b
> to no avail. Tried all available block numbers that are listed
> when original mkfs was done, and it's output was save
On 09/18/2014 01:23 PM, Tom Horsley wrote:
On Thu, 18 Sep 2014 12:45:37 -0600
jd1008 wrote:
I was also looking for the formula that is used to compute the location
of all of the backup superblocks.
OK, I found my notes from the last time I did this the paragraph about
units may be the importa
On Thu, 18 Sep 2014 12:45:37 -0600
jd1008 wrote:
> I was also looking for the formula that is used to compute the location
> of all of the backup superblocks.
OK, I found my notes from the last time I did this the paragraph about
units may be the important part :-).
I was able to mount the buste
On 09/18/2014 11:42 AM, Nathan Schwarz wrote:
Unmount the partition, `debugfs $partition` and then `extract
$fileOnDamagedFilesystem $targetFileOnExternalFilesystem`. That should
do it - but you should check the man-page since I can't recall if it was
exactly that.
- Nathan
Thank you Nathan.
On 09/18/2014 12:57 PM, Rick Stevens wrote:
On 09/18/2014 11:45 AM, jd1008 issued this missive:
I have been searching for ext2/3 design docs to see where the on-disk
superblock is located relative to starting sector of the partition,
and how
many bytes it occucpies.
I was also looking for t
On 09/18/2014 11:45 AM, jd1008 issued this missive:
I have been searching for ext2/3 design docs to see where the on-disk
superblock is located relative to starting sector of the partition, and how
many bytes it occucpies.
I was also looking for the formula that is used to compute the location
I have been searching for ext2/3 design docs to see where the on-disk
superblock is located relative to starting sector of the partition, and how
many bytes it occucpies.
I was also looking for the formula that is used to compute the location
of all of the backup superblocks.
Thnaks for any poi
On 09/18/2014 11:58 AM, Tom Horsley wrote:
I recently got some files off a damaged disk by mounting
it using an alternate superblock (I don't remember any details,
but I know I found how to do it via google searches).
Non of the alternate superblock I tried worked.
All of them have bad magic.
A
I recently got some files off a damaged disk by mounting
it using an alternate superblock (I don't remember any details,
but I know I found how to do it via google searches).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproj
Unmount the partition, `debugfs $partition` and then `extract
$fileOnDamagedFilesystem $targetFileOnExternalFilesystem`. That should
do it - but you should check the man-page since I can't recall if it was
exactly that.
- Nathan
--
/"\ ASCII Ribbon Campaign
\ / - against HTML emails
X - aga
Is there any other tool that can extract files from a partition that
seems to have corrupted superblocks?
I tried dumpe2fs, and fsck -b
to no avail. Tried all available block numbers that are listed
when original mkfs was done, and it's output was saved.
None of the blocks seem to work - all of
32 matches
Mail list logo
