I don't know if there's any easy way to delete them, but I can offer a
suggestion for the future.
Tim Foster has a ZFS automatic snapshot script that would be worth taking a
look at:
http://blogs.sun.com/timf/entry/zfs_automatic_snapshots_0_10
That script lets you fairly easily set up
zfs list is mighty slow on systems with a large number of objects, but there is
no foreseeable plan that I'm aware of to solve that problem.
Never the less, you need to do a zfs list, therefore, do it once and work from
that.
zfs list /tmp/zfs.out
for i in `grep mydataset@ /tmp/zfs.out`; do
Sylvain Dusart schrieb:
Hi Joe,
I use this script to delete my empty snapshots :
#!/bin/bash
NOW=$(date +%Y%m%d-%H%M%S)
POOL=tank
zfs snapshot -r [EMAIL PROTECTED]
FS_WITH_SNAPSHOTS=$(zfs list -t snapshot | grep '@' | cut -d '@' -f 1 | uniq)
for fs in $FS_WITH_SNAPSHOTS ; do
On Thu, 17 Jul 2008, James C. McPherson wrote:
I don't understand what you mean by Odd requirement to update
/etc/vfstab
- when we turn on mpxio the device paths change, so any fs that's not
ZFS will require repointing, as it were. One of the issues I've come
It was a design choice to
On Thu, 17 Jul 2008, Ben Rockwood wrote:
zfs list is mighty slow on systems with a large number of objects,
but there is no foreseeable plan that I'm aware of to solve that
problem.
Never the less, you need to do a zfs list, therefore, do it once and
work from that.
If the snapshots
Hello,
I recently installed SunOS 5.11 snv_91 onto a Ultra 60 UPA/PCI with OpenBoot
3.31 and two 300GB SCSI disks. The root file system is UFS on c0t0d0s0.
Following the steps in ZFS Admin I have attempted to convert root to ZFS
utilizing c0t1d0s0. However, upon init 6 I am always presented
Hi Joe,
It is possible that your c0t1d0s0 disk has an existing EFI label instead
of a VTOC label?
(You can tell by using format--disk--partition and see
if the cylinder info is displayed. If no cylinder info, then an EFI
label.)
Relabel with a VTOC label, like this:
# format -e
select disk
I would like to request an additional flag for the command line zfs
tools. Specifically, I'd like to have a -t flag for zfs destroy, as
shown below. Suppose I have a pool home with child filesystem
will, and a snapshot home/[EMAIL PROTECTED]. Then I run the
following commands:
# zfs destroy -t
zfs destroy -t flag
Thumbs up for this.
Plus asking for an -i flag, for interactive mode, handy on things like
zfs destroy.
-mg
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I've looked for anything I can find on the topic, but there does not
appear to be anything documented.
Can a ZVOL be expanded?
In particular, can a ZVOL sharded via iscsi be expanded?
Thanks,
Charles
___
zfs-discuss mailing list
On Thu, Jul 17, 2008 at 04:28:34PM -0400, Charles Menser wrote:
I've looked for anything I can find on the topic, but there does not
appear to be anything documented.
Can a ZVOL be expanded?
I think setting the volsize property expands it. Dunno what happens on
the clients though.
--
http://www.opensolaris.org/bug/report.jspa
You'll need an OpenSolaris.org account to file the RFE of course.
On Jul 17, 2008, at 10:52 AM, Will Murnane wrote:
I would like to request an additional flag for the command line zfs
tools. Specifically, I'd like to have a -t flag for zfs destroy,
Will Murnane wrote:
On Thu, Jul 17, 2008 at 17:05, Chad Lewis [EMAIL PROTECTED] wrote:
http://www.opensolaris.org/bug/report.jspa
You'll need an OpenSolaris.org account to file the RFE of course.
Thanks for the link. I've filed an RFE, but don't see it yet; is
there a better way than text
In one of my prior experiments, I included the names of the snapshots I
created in a plain text file.
I used this file, and not the zfs list output to determine which
snapshots I was going to remove when it came time.
I don't even remember *why* I did that in the first place, but it
certainly
We just got a new system to use as a zfs file server with 8 drives on 2
controllers. I've installed on and mirrored c4t0d0s0 and c5t0d0s0, and am now
trying to create a mirrored set out of the rest of the disks, however all of
them are giving me i/o errors, e.g.:
# uname -a
SunOS
I ran a scrub on a root pool after upgrading to snv_94, and got checksum
errors:
pool: r00t
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are
unaffected.
action: Determine if the device needs
Alan wrote:
We just got a new system to use as a zfs file server with 8 drives on 2
controllers. I've installed on and mirrored c4t0d0s0 and c5t0d0s0, and am
now trying to create a mirrored set out of the rest of the disks, however all
of them are giving me i/o errors, e.g.:
# uname -a
I swear I tried that and got file not found, but lo! it worked. argh!
thanks...
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Wed, Jul 09, 2008 at 11:18:23PM -0500, Florin Iucha wrote:
On Wed, Jul 09, 2008 at 06:02:24PM -0700, Brandon High wrote:
Here's the component list that I'm planning to use right now:
http://secure.newegg.com/WishList/PublicWishDetail.aspx?Source=MSWDWishListNumber=7739092
this looks
19 matches
Mail list logo
