Ok, tested this myself ...
(same hardware used for both tests)
OpenSolaris svn_104 (actually Nexenta Core 2):
100 Snaps
r...@nexenta:/volumes# time for i in $(seq 1 100); do zfs snapshot
ssd/v...@test1_$i; done
real0m24.991s
user0m0.297s
sys 0m0.679s
Import:
comment below...
On Jan 11, 2010, at 10:00 AM, Lutz Schumann wrote:
Ok, tested this myself ...
(same hardware used for both tests)
OpenSolaris svn_104 (actually Nexenta Core 2):
100 Snaps
r...@nexenta:/volumes# time for i in $(seq 1 100); do zfs snapshot
One thing which may help is the zfs import was single threaded, ie it open
every disk one disk (maybe slice) at a time and processed it, as of 128b it is
multi-threaded, ie it opens N disks/slices at once and process N disks/slices
at once. When N is the number of threads it decides to use.
Cause you mention the fixed / bugs I have a more general question.
Is there a way to see all commits to OSOL that are related to a Bug Report ?
Background: I'm interested in how e.g. the zfs import bug was fixed.
--
This message posted from opensolaris.org
.. however ... a lot of snaps still have a impact
on system performance. After the import of the 1
snaps volume, I saw devfsadm eating up all CPU:
If you are snapshotting ZFS volumes, then each will
create an entry in the
device tree. In other words, if these were file
systems
Lutz,
On Mon, Jan 11, 2010 at 09:38:16PM -0800, Lutz Schumann wrote:
Cause you mention the fixed / bugs I have a more general question.
Is there a way to see all commits to OSOL that are related to a Bug Report ?
You can go to : src.opensolaris.org and give the bug-id in the history field
By having a snapshot you
are not releasing the
space forcing zfs to allocate new space from other
parts of a disk
drive. This may lead (depending on workload) to more
fragmentation, less
localized data (more and longer seeks).
ZFS uses COW (copy on write) during writes. This means
On 08/01/2010 12:40, Peter van Gemert wrote:
By having a snapshot you
are not releasing the
space forcing zfs to allocate new space from other
parts of a disk
drive. This may lead (depending on workload) to more
fragmentation, less
localized data (more and longer seeks).
ZFS uses COW
On Fri, January 8, 2010 07:51, Robert Milkowski wrote:
On 08/01/2010 12:40, Peter van Gemert wrote:
By having a snapshot you
are not releasing the
space forcing zfs to allocate new space from other
parts of a disk
drive. This may lead (depending on workload) to more
fragmentation, less
On 08/01/2010 14:50, David Dyer-Bennet wrote:
On Fri, January 8, 2010 07:51, Robert Milkowski wrote:
On 08/01/2010 12:40, Peter van Gemert wrote:
By having a snapshot you
are not releasing the
space forcing zfs to allocate new space from other
parts of a disk
drive. This may lead
On Fri, 8 Jan 2010, Peter van Gemert wrote:
I don't think the use of snapshots will alter the way data is
fragmented or localized on disk.
What happens after a snapshot is deleted?
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
Lutz Schumann presa...@storageconcepts.de writes:
When importing a pool with many snapshots (which happens during
reboot also) the import may take a long time (example: 1
snapshots ~ 1-2 days).
I've not tested the new release of Solaris (svn_125++) which fixes
this regarding this issue.
Snapshots do not impact write performance. Deletion of the snapshots seems to
be also a constant operation (time taken = number of snapshots x some time).
However see http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6761786.
When importing a pool with many snapshots (which happens
On 06/01/2010 11:03, Lutz Schumann wrote:
Snapshots do not impact write performance. Deletion of the snapshots seems to
be also a constant operation (time taken = number of snapshots x some time).
that's not entirely true. By having a snapshot you are not releasing the
space forcing zfs
Is there any limit on the number of snapshots in a file system?
The documentation -- manual page, admin guide, troubleshooting guide
-- does not mention any. That seems to confirm my assumption that is
is probably not a fixed limit, but there may still be a practical
one, just like there is no
Juergen Nickelsen wrote:
Is there any limit on the number of snapshots in a file system?
The documentation -- manual page, admin guide, troubleshooting guide
-- does not mention any. That seems to confirm my assumption that is
is probably not a fixed limit, but there may still be a practical
16 matches
Mail list logo
