xfs
[Top] [All Lists]

Re: XFS File system in trouble

To: xfs@xxxxxxxxxxx
Subject: Re: XFS File system in trouble
From: Martin Papik <mp6058@xxxxxxxxx>
Date: Tue, 28 Jul 2015 22:12:00 +0300
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Z4MWUBgVcHZbPyF4JWlEO/8bDzUA1HUh77hiUEJ01TU=; b=yaaBMtl7NFvQ0IgjyhWI6JjRgblef4s9/tkqBBI1Sk1r3J3d7i6MbXCU5yq82HLix+ wVjIbzSELyvuU997STkz+kxDPA1DFxtfQN/D60dJDScpXG8sNt2GBahSlUE4FBmh6bny kog72vuTVH+dpZpfbyQ6ZVGGnX7He7encONOl6Vx+UQ3cnshS5h8M96VAHr63i3MvX/d RTCuP0PR6fQPPIvCfP6gEmKzqCc4GrjvhUerOkTHbWOkn9Cd+Db/TJ9CqsKNTIet13/A gu0IFIFBAZWPWYcpjuwQd9/Sdr0T+LOvmjFKIZEoVU9sZfGSxyAEj898DtWb77BOXNoZ OmHg==
In-reply-to: <55B7B390.1050206@xxxxxxxxxxx>
References: <03864DDC681E664EBF5D47682BE7D7CF0D3574DF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <55AA5FCE.4080702@xxxxxxxxxxx> <03864DDC681E664EBF5D47682BE7D7CF0D358740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAN3tLtJuk3LKHtxvbXATBR7bjr2e=GTX-fgs-jQniuxqRXjeoA@xxxxxxxxxxxxxx> <55AAF73A.4040903@xxxxxxxxxxxx> <20150720111747.GA53450@xxxxxxxxxxxxxxx> <55B73365.1050908@xxxxxxxxxxxx> <20150728123307.GC38784@xxxxxxxxxxxxxxx> <55B79BFD.6020509@xxxxxxxxxxxx> <55B7B390.1050206@xxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


How about this?

qemu-img create -f qcow2 test 32T
qemu-nbd -c /dev/nbd0 test
xfs_mdrestore -g md0.metadump /dev/nbd0



>>> 
>>> Hmm, I guess the file size exceeds the capabilities of the root
>>> fs, even if there might ultimately be enough space to restore
>>> the metadump.
>> 
>> I wouldn't think so, at least not fundamentally. It's ext4. It's 
>> certainly not big enough to hold an 18T file system, though, and 
>> perhaps that is what xfs_restore is checking.
> 
> No, it's just failing to write any data at an 18T offset.
> 
> The ext4 filesystem (with 4k blocks) is limited to a 16T maximum
> file offset; you won't be able to restore a (sparse) 18T
> filesystem image onto an ext4 filesystem.

>> 
>> RAID-Server:/TEST# xfs_mdrestore -g md0.metadump RAIDfile.img 
>> xfs_mdrestore: cannot set filesystem image size: File too large
>> 
> 
> Hmm, I guess the file size exceeds the capabilities of the root fs,
> even if there might ultimately be enough space to restore the
> metadump.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVt9P3AAoJELsEaSRwbVYryxEP/1WDJUO15CA35VW/JE13gp/U
qIXsc8tS3ZKds/at1boPAw2/X4HYclfuhV9heYi+npzF/0pimqTY7MkjxVN3JUHf
r2pOZSL0r0YqPw0Wc17sFOY5y1F7AzHS9vIUIMpYTW5A0CasQDUCuetfhlawNWLR
ijjmXWnLivPo7tsIOC7WMl9wmf3kO9P/2wN0aR5oUmtcdn4sPiqPHYv1e6UpiYkr
Qv1M1NtX9rryLQZyWWtHQQGj+3IFyMIT6NszQ8mOPw8ijJTxMlVb5rxyP4I5uzZw
r0KkIWxfU558I/eGHaVHlsWBpaqM5JbiZzQDkh03vCIyZNi5tnwDKl0i2wRsM6m/
N7VvUSwDHOvoxpQtE3KYVcOqlyGXS/S2N6wSBDQ5LqSQDS8JRJYt2wjnaSNG2ib7
ddLlfkGhkM4IDpWjn0HvupDY9jhcKDxEpZ8t73tQLSaq705GYMcYxOmplzM6Iu3E
it7oiCM/p76p5NF5BLqoj1zU/XFKgpadcTOkL6vNjVvDzjhVO/RL8lS7yI8dbHuk
t44SN5jCX+OmawxveAaXs1BSySCgOEK/kZuYYNvrIZq0W3ZoeLJKNFUtuOr24Kwn
HY8/GyRxG9Kg4+KoUvV6skZw+/RjEgDGJ17vVHc23qVfSraJftXjiE42Hp2BI4NK
RHVCtUzI+6fK7xL2Ex06
=Oqcp
-----END PGP SIGNATURE-----

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