On Mon, 24 Jul 2000, jones@xxxxxxxxxxxxxxxxxx wrote:
> Given the need to handle file attributes and other xfs file extensions
> I don't see how a program that dumps a xfs file can produce a dump
> tape compatible with the current linux dump/restore.
> I think a better solution would be to add the xfs ioctl'shat
> xfs_restore/xfs_dump need to the ext2 file system. Not all the
> xfs_ioctl need to fully work they just need to return reasonable
> default values. That way their need only be one dump/restore program
> for linux.
> I understand the wish for all dump/restore programs to work the same
> way but given the different capabilities of the various unix file
> systems that just not possible.
> Bill Jones
Just thought I'd clarify what's going on...
1. xfs dump -> xfs works - xfsrestore
2. xfs -> xfs dump works - xfsdump
3. xfs dump -> ext2 not yet
4. xfs -> linux dump not yet
5. ext2 -> xfs dump not yet
6. linux dump -> xfs works - linux restore
1 & 2 As Ken said, xfsdump & xfsrestore are getting close to being
useful. They should be released to the public as soon as we get
the endian conversion done - the objective is to have the tape
format to be compatible with the IRIX version.
3 Might work with little effort.
4 This would be a change to linux dump to support xfs, and might
just mean writing a small set of functions to replace the calls
to the ext2 library.
5 This wouldn't be too useful, unless people really prefer xfsdump,
or want to just use one dump program.
6 I ran the linux restore once, and it seemed to have no problem
writing to an xfs filesystem.
As for having several versions of dump, xfsdump/xfsrestore are _very_
different from the linux versions. To somehow merge their functionality
would be too time consuming to be worth the effort, especially at this
stage. Keep in mind, that one of our goals is to make Linux friendly for
IRIX people, so we'd like to keep the wizbang functionality of the IRIX
xfsdump/xfsrestore, and likewise, I'm sure Linux folk who rely on
dump/restore, wont want to change to our version until it has been proven
to be as reliable and more useful. I've no doubt it will be a headache
when every filesystem has its own version of dump/restore - but it'd be
better, I think, to wait for the dust to settle a bit, before worrying
about some sort of consolidation.
Also, there is still a fair check list of things left to do in
xfsdump/xfsrestore, even after the endian conversion and we release it.