James Carlson <[EMAIL PROTECTED]> wrote on 01/08/2007 03:26:14 PM:
> [EMAIL PROTECTED] writes:
> > > I was noodling around with creating a backup script for my home
> > > system, and I ran into a problem that I'm having a little trouble
> > > diagnosing. Has anyone seen anything like this or have any debug
> > > advice?
> > >
> > > I did a "zfs create -r" to set a snapshot on all of the members of a
> > > given pool. Later, for reasons that are probably obscure, I wanted
to
> > > rename that snapshot. There's no "zfs rename -r" function, so I
tried
> > > to write a crude one on my own:
> >
> > do you mean "zfs snapshot -r <fsname>@foo" instead of the create?
>
> Yes; sorry. A bit of a typo there.
>
> > hmm, just to verify sanity, have can you show the output of:
> >
> > zfs list -rHo name -t filesystem pool
> >
> > and
> >
> > zfs list -rHo name -t filesystem pool |
> > while read name; do
> > echo zfs rename [EMAIL PROTECTED] [EMAIL PROTECTED]
> > done
> >
> > (note the echo inserted above)
>
> Sure, but it's not a shell problem. I should have mentioned that when
> I brought the system back up, *most* of the renames had actually taken
> place, but not *all* of them. I ended up with mostly [EMAIL PROTECTED], but
> with a handful of stragglers near the end of the list [EMAIL PROTECTED]
>
> The output looks a bit like this (not _all_ file systems shown, but
> representative ones):
>
> pool
> pool/HTSData
> pool/apache
> pool/client
> pool/csw
> pool/home
> pool/home/benjamin
> pool/home/beth
> pool/home/carlsonj
> pool/home/ftp
> pool/laptop
> pool/local
> pool/music
> pool/photo
> pool/sys
> pool/sys/core
> pool/sys/dhcp
> pool/sys/mail
> pool/sys/named
>
> And then:
>
> zfs rename [EMAIL PROTECTED] [EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/home/[EMAIL PROTECTED] pool/home/[EMAIL PROTECTED]
> zfs rename pool/home/[EMAIL PROTECTED] pool/home/[EMAIL PROTECTED]
> zfs rename pool/home/[EMAIL PROTECTED] pool/home/[EMAIL PROTECTED]
> zfs rename pool/home/[EMAIL PROTECTED] pool/home/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/[EMAIL PROTECTED] pool/[EMAIL PROTECTED]
> zfs rename pool/sys/[EMAIL PROTECTED] pool/sys/[EMAIL PROTECTED]
> zfs rename pool/sys/[EMAIL PROTECTED] pool/sys/[EMAIL PROTECTED]
> zfs rename pool/sys/[EMAIL PROTECTED] pool/sys/[EMAIL PROTECTED]
> zfs rename pool/sys/[EMAIL PROTECTED] pool/sys/[EMAIL PROTECTED]
>
> It's not a matter of the shell script not working; it's a matter of
> something inside the kernel (perhaps not even ZFS but instead a driver
> related to SATA?) experiencing vapor-lock.
>
> Other heavy load on the system, though, doesn't cause this to happen.
> This one operation does cause the lock-up.
>
Understood. Two things, does the rename loop hit any of the fs in
question, and does putting a " sort -r | " before the while make any
difference?
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
