xfs
[Top] [All Lists]

Re: how cant I rebuild the superblock

To: Steve Lord <lord@xxxxxxx>
Subject: Re: how cant I rebuild the superblock
From: Sven Gehr <sven@xxxxxxxxxxxxx>
Date: Wed, 30 Mar 2005 17:58:52 +0200 (CEST)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <424AC78C.70708@xxxxxxx>
Organization: dreampixel
References: <2545159.1112195262796.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <424AC78C.70708@xxxxxxx>
Reply-to: sven@xxxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
Am Mi 30.03.2005 17:36 schrieb Steve Lord <lord@xxxxxxx>:
> Sven Gehr wrote:
> >  Am Mi 30.03.2005 15:36 schrieb Steve Lord <lord@xxxxxxx>:

Hallo,

[...]
> The file size you need is 142287360 * 1024, or 145702256640
> 
> try:
> 
> dd if=/dev/zero of=/tmp/sparse bs=1024 count=1 seek=142287359
> 
> mkfs -t xfs -d file -d size=145702256640 -d name=/tmp/sparse

ok, I have the sparse file generate.

> Now, the only problem with this is that if you used any special
> parameters on your original mkfs line, they are missing here.

I have the orginal xfs on the suse 9.1 machine with yast without modify
the parameter.

> Since they are stored in the superblock, you are rather stuck if you
> cannot remember them.

[...]
> do dd if=/dev/md0 of=/tmp/block bs=16k count=1

> then do od -xa on this file and send the output to the list, it will
> be fairly simple to see if you lost more than the super block.

the output is in the attachment file. I hope the list accept mails with
attachments?

 
> If there are alternate superblocks, then xfs_repair can usually find
> them. What led you down the path of wanting to rebuild your super
> block in the first place?

The xfs_repair tell me there is no alternate superblock.

with best regards
sven

Attachment: od_block_output
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>