On Tue, Aug 05, 2014 at 01:06:42AM +0200, Marcin Wolcendorf wrote:
>
> Is it possible to somehow extract the FS structures so it would be easier to
> experiment with this? I mean - if the FS structures take less space, I could
> store them and reclaim those puny 16TB; maybe some sparse image file would do?
> I'd be quite happy to help here, but I need guidance.
> Still, I would like to clean up all this mess I'm in - I (hopefully) have some
> data on this FS, that I would like to move away, but without resize2fs I do
> not
> have enough space.
Yes, you can --- see the "RAW IMAGE FILES" section of the e2image
program. Unfortunately, ext4 doesn't support logical file lengths >
4TB, so in order to use this I would need to expand the sparse file
onto an xfs filesystem, but that's OK, I've done that sort of thing
before.
That being said, I'm pretty sure the problem will evaporate once we
move it to a raw image file --- the short write is something which is
fundamental to the block device, not the file system image.
> > I could send you instructions on how to build a patched e2fsprogs to
> > see if the workaround works, but even if it does, I'm very hesitant
> > about whether this is something I would be willing to check in.
>
> As I said, I'd be happy to investigate some more, but then again - I'd like to
> have my disk space back, and preferably not by removing the home_move_tmp.
> So if it is possible, I would like the patched resize2fs (or instructions to
> patch it), and maybe some instructions how to dump/preserve the current FS
> structures for further investigation.
Ok, do the following:
git clone -b retry-write git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
e2fsprogs-retry
cd e2fsprogs-retry
./configure
make -j8
Then try using the resize/resize2fs and see if that works any better for you.
If you can try to save a compressed raw image file, that would be
nice, but I expect the problem is device specific, as I mentioned
earlier.
Cheers,
- Ted
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
