da2 at twa0 bus 0 scbus0 target 2 lun 0
da3 at twa0 bus 0 scbus0 target 3 lun 0
da4 at twa0 bus 0 scbus0 target 4 lun 0
Are these all JBOD devices?
--
Peter Jeremy
pgpykCYjUFT7j.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
.
The damage exists in the oldest snapshot for that filesystem.
--
Peter Jeremy
pgpxQIIBICxmG.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 2012-Nov-19 13:47:01 -0500, Ray Arachelian r...@arachelian.com wrote:
On 11/19/2012 12:03 PM, Peter Jeremy wrote:
The damage exists in the oldest snapshot for that filesystem.
Are you able to delete that snapshot?
Yes but it has no effect - the corrupt object exists in the current
pool so
On 2012-Nov-19 21:10:56 +0100, Jim Klimov jimkli...@cos.ru wrote:
On 2012-11-19 20:28, Peter Jeremy wrote:
Yep - that's the fallback solution. With 1874 snapshots spread over 54
filesystems (including a couple of clones), that's a major undertaking.
(And it loses timestamp information).
Well
to be documented as a caveat on zfs diff -
especially since it can cause hangs and panics with older kernel code.
--
Peter Jeremy
pgpFsaNn4GfUQ.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org
in the pool).
--
Peter Jeremy
pgpi6E6cZupsp.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
with FreeBSD
9.0 and ZFS 28 but I didn't want to make any basic design mistakes in
doing this.
I'd suggest you test 9.1-RC2 (just released) with a view to using 9.1,
rather than installing 9.0.
Since your questions are FreeBSD specific, you might prefer to ask on
the freebsd-fs list.
--
Peter Jeremy
prebuilt distro (I don't know of other
builds with that - feature integrated into code this summer).
FreeBSD-head does.
--
Peter Jeremy
pgpaswWHOLhMp.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
=2.
b) Attempt to rebuild your laptop and restore from backups (left securely
at home) via the dodgy hotel wifi.
--
Peter Jeremy
pgpvosNQQa9DJ.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
it'll be available in ZFS in the near future.
--
Peter Jeremy
pgpNyzMT6fOdD.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
on a later
munmap(2) and it should always be safe to call msync(MS_ASYNC) before
munmap(2) (in fact, it's a good idea to maximise portability).
--
Peter Jeremy
pgp7hDyys4IEu.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
fragmented. If you do try this,
I'd recommend creating a snapshot first and then rolling back to it,
rather than just deleting the junk file. Also, this (obviously) won't
work at all on a filesystem with compression enabled.
--
Peter Jeremy
pgpwHwVLcSvcK.pgp
Description: PGP signature
written in (2) can be read.
7) Argue with drive vendor that drive doesn't meet specifications :-)
A similar approach can also be used to verify that NCQ cache flush
commands actually work.
--
Peter Jeremy
pgp4WNXKBfWaW.pgp
Description: PGP signature
the drive cache enabled
in either situation. I'm not sure how OI or Linux behave.
--
Peter Jeremy
pgprzpycAxFkZ.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs
) disk in the target pool?
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
.
--
Peter Jeremy
pgpe2tUImniF1.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
of snapshots and a fair amount
of activity. A scrub takes around 17 hours.
This is another area where the mythical block rewrite would help a lot.
--
Peter Jeremy
pgpH1dpSOBHnT.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
a
lower-performance (cheaper) SSD.
--
Peter Jeremy
pgpoOozgavEXj.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
in either
mode. ZFS makes it easier to switch modes because it doesn't care
about the actual device name - at worst, you will need an export and
import.
--
Peter Jeremy
pgpHPygB4VeNl.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
port from reading (and
maybe even writing to) the pool.
--
Peter Jeremy
pgpj1BokjEkft.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
be a disadvantage).
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
compression isn't supported - at least
in v15, trying to make a gzip compressed filesystem bootable or trying
to set compression=gzip on a bootable filesystem gives a very
uninformative error message and it took a fair amount of trawling
through the source code to find the real cause.
--
Peter
.
Hopefully a silly question but does the SB1000 support USB2? All of
the Sun hardware I've dealt with only has USB1 ports.
And, BTW, 2GB RAM is very light on for ZFS (though I note you only
have a very small amount of data).
--
Peter Jeremy
pgp8UazHZQHJM.pgp
Description: PGP signature
to the backup host).
--
Peter Jeremy
pgpn3inOqECRR.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
be better
switching to nexenta or openindiana or solaris 11 express, because they all
support ZFS much better than freebsd.
I'm primarily interested in running FreeBSD and will be upgrading to
ZFSv28 once it's been shaken out a bit longer.
--
Peter Jeremy
pgp0CAxj3Ebk1.pgp
Description: PGP
:872819992] dataset = 469
2011-03-17.11:30:13 zfs rollback zroot/home@20110309
2011-03-17.12:01:02 zfs recv -vd zroot
2011-03-17.12:03:57 [internal rollback txg:872820399] dataset = 469
2011-03-17.12:03:57 zfs rollback zroot/home@20110309
--
Peter Jeremy
pgpQBYUCWUiu1.pgp
Description: PGP signature
or rebuild your pool (via send/recv or similar).
--
Peter Jeremy
pgp2oCcOvB9YH.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
the time-to-notice plus time-to-resilver before regaining
redundancy. The downside is that actively using the hot spare
may increase the probability of it failing.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
is
missing - which might let me recover it in other ways.
--
Peter Jeremy
pgppzMAxBmwjV.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
view
of the physical disks. It might also be worthwhile looking at a hexdump
of the first and last few MB of the faulty disks - it's possible that
the controller has decided to just shift things by a few sectors so the
labels aren't where ZFS expects to find them.
--
Peter Jeremy
of floating point within the kernel also means changes to
when FPU context is saved - and, unless this can be implemented
lazily, it will adversely impact the cost of all context switches
and potentially system calls.
--
Peter Jeremy
pgphVXYz2zc3s.pgp
Description: PGP signature
I'm subscribed to where signatures
get mangled.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
of evidence and clues
if I only knew how to look for them, in the logs.
Serious hardware problems are unlikely to be in the logs because the
system will die before it can write the error to disk and sync the
disks. You are more likely to see a problem on the console.
--
Peter Jeremy
?
With care, nothing.
--
Peter Jeremy
pgpN6MGlBBoFC.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
that adding disks to them is a routine operation; to the
extent that that's a problem, that really needs to be fixed.
It will (should) arrive as part of the mythical block pointer rewrite project.
--
Peter Jeremy
pgpy4W6UFItyz.pgp
Description: PGP signature
KB.
--
Peter Jeremy
pgp8Dn2Yb6bMc.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
the applications trying to write will suspend. What would be the
risk of that?
At least some versions of Oracle rdbms have timeouts around I/O and
will abort if I/O operations don't complete within a short period.
--
Peter Jeremy
pgp1r1gM7cLEs.pgp
Description: PGP signature
disk in each mirror pair can fail.
With a mirror, Murphy's Law says that the second disk to fail will be
the pair of the first disk :-).
--
Peter Jeremy
pgpqLss4mZKH3.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
instead of getting custom firmware for their CD drives to make
them provide 512-byte logical blocks for 2KB CD-ROMs.
It's even more idiotic of WD to sell a drive with 4KB sectors but
not provide any way for an OS to identify those drives and perform
4KB aligned I/O.
--
Peter Jeremy
about what happens if you find a silent bit corruption in
a file system that includes encrypted files.
Or compressed files.
--
Peter Jeremy
pgp2gl67ZdR99.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
... then the mountpoint gets replicated and
the backup gets mounted over the top of my real filesystems.
- If I skip the '-R' then none of the properties get backed up.
Is there some way to have zfs recv not automatically mount filesystems
when it creates them?
--
Peter Jeremy
pgpOliK2tC1Vs.pgp
Description: PGP
is at least
as important as whether it's 32-bit or 64-bit.
--
Peter Jeremy
pgpSec5hUa4mU.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
but they
can put a different (non-OSS) license on any new code.
--
Peter Jeremy
pgpuCWzXnMlHq.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 2010-Jul-27 19:43:50 +0800, Andrey V. Elsukov bu7c...@yandex.ru wrote:
On 27.07.2010 1:57, Peter Jeremy wrote:
Note that ZFS v15 has been integrated into the development branches
(-current and 8-stable) and will be in FreeBSD 8.2 (or you can run it
ZFS v15 is not yet in 8-stable. Only
be downloaded).
See http://www.freebsd.org/releases/8.1R/announce.html
--
Peter Jeremy
pgppFbh5U0Jj5.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
at the time of the send.
If you have sufficient free space, you can even do a send|recv on the
same system - but if the original fileset was mounted that this will
result in the new fileset being mounted over the top of it, so you
shouldn't do this on an active system.
--
Peter Jeremy
publicise it widely as you have broken that hash function.
--
Peter Jeremy
pgpiebzGoklvU.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
know other companies with similar policies. And getting approval
for a couple of thousand dollars of new disks is very much easier than
getting approval for a complete new SAN with (eg) twice the capacity
of the existing one.
--
Peter Jeremy
___
zfs
segregated (note the 'gnu' in the above URI).
--
Peter Jeremy
pgpvmgKqx7nJf.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
and trying to import the original zpool from the detached files.
--
Peter Jeremy
pgp5OU8Gba0CI.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
'
was traditionally implemented. Note that you need to check device and
inode, not just inode, to correctly handle mountpoints.
--
Peter Jeremy
pgpsc9geRSx95.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
more significant change and the utility is not clear.
Also not trivial, it's certainly possible to make all this information
available under proposed directories, .zfs/inodes or something similar.
HP Tru64 already does something like this.
--
Peter Jeremy
pgp2nCFDIdxia.pgp
Description: PGP
and
restore it later, this will recover your existing boot and swap so you
shouldn't need to restore them.
--
Peter Jeremy
pgpHLIUCADaBM.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org
is to (temporarily) change the disk
slicing so that there is a fdisk slice that matches ad6s1d.
--
Peter Jeremy
pgpuiR7yDRv37.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman
() and rmdir() to manage the
backlinks (taking into account transactional consistency).
--
Peter Jeremy
pgpLmGCkPtpSv.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
, Oracle
contracts are deliberately designed so you can't be certain whether
you are compliant or not.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I
freed up a few percent more space, the performance recovered.
Maybe it would be useful if ZFS allowed the reserved space to be
tuned lower but, at least for ZFS v13, the reserved space seems to
actually be a bit less than is needed for ZFS to function reasonably.
--
Peter Jeremy
on
i386). It may be possible to reuse some of that code.
--
Peter Jeremy
pgp0WiQELKoEj.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
.
--
Peter Jeremy
pgpC0sjEufK37.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
congruential generator,
lagged fibonacci generator, mersenne twister or even random(3)
http://en.wikipedia.org/wiki/List_of_random_number_generators
--
Peter Jeremy
pgpO9mAWzbb7x.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss
the relevant ZFS bits for my b127 system but
haven't managed to get them to work so far.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
copies of metadata are written at the same time, it
cannot protect against failures localized in time.
Thanks for that. I suspected it might be something like this.
--
Peter Jeremy
pgpTbho8x8cyp.pgp
Description: PGP signature
___
zfs-discuss mailing
that metadata is triplicated, where did the objset go?
--
Peter Jeremy
pgpcSxvFaLwUM.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
63 matches
Mail list logo
