joerg.schill...@fokus.fraunhofer.de (Joerg Schilling) writes: > Harry Putnam <rea...@newsguy.com> wrote: > >> Dennis Clarke <dcla...@blastwave.org> writes: >> >> > This will probably get me bombed with napalm but I often just >> > use star from Jörg Schilling because its dead easy : >> > >> > star -copy -p -acl -sparse -dump -C old_dir . new_dir >> > >> > and you're done.[1] >> > >> > So long as you have both the new and the old zfs/ufs/whatever[2] >> > filesystems mounted. It doesn't matter if they are static or not. If >> > anything changes on the filesystem then star will tell you about it. >> >> I'm not sure I see how that is easier. >> >> The command itself may be but it requires other moves not shown in >> your command. > > Could you please explain your claims?
Well it may be a case of newbie shooting off mouth on basis of small knowledge but the setup you showed with star does not create a zfs filesystem. I guess that would have to be done externally. Whereas send/receive does that part for you. My first thought was rsync... as a long time linux user... thats where I would usually turn... until other posters pointed out how send/receive works. i.e. It creates a new zfs filesystem for you, which was exactly what I was after. So by using send/receive with -u I was able in one move to 1) create a zfs filesystem 2) mount it automatically 3) transfer the data to the new fs `star' only does the last one.... right? I then had a few external chores like setting options or changing mountpoint. Something that would have had to be done using `star' too. (That is, before using star) That alone was the basis of what you call my `claims'. Would `star' move or create the .zfs directory? _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
