arget 0 lun 0
>da1 at twa0 bus 0 scbus0 target 1 lun 0
>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
I assumed that ZFS reset the
parent to "unknown" rather than leaving it as a pointer to a random
no-longer-valid object.
This probably needs to be documented as a caveat on "zfs diff" -
especially since it can cause hangs and panics with older kernel code.
--
Pete
On 2012-Nov-19 21:10:56 +0100, Jim Klimov 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 time
On 2012-Nov-19 13:47:01 -0500, Ray Arachelian 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 del
ing.
(And it loses timestamp information).
--
Peter Jeremy
pgpxBLIU3wbVi.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
t if you know the damage is recent.
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
at is a last resort (since there
are 54 filesystems and ~1900 snapshots 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
starts slowing down?
> so I was planning to rebuild the server 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 qu
re flags, and that is currently
>supported by oi_151a5 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
ly repair the sector thanks to copies=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://mail.opensolaris.org/mailman/listinfo/zfs-discuss
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
but if you want a guarantee that your data is
securely written to stable storage then you need to wait for that
stable storage. msync(MS_ASYNC) should have no impact 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 maximi
ld leave your drive seriously 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 compressi
y
6) Verify data 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
___
verhead there. FreeBSD leaves 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://ma
a dying (or dead) disk in the target pool?
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
ining a
mirrored root with RAIDZ data aren't that great. At home, I have 6
1TB disks and I've carved out 8GB from the front of each (3GB for swap
and 5GB for root) and the remainder in a RAIDZ2 pool - that's less
than 1% overhead. 5GB is big enough to hold the comple
s seldom needed at
>my former site once UFS journalling
>became available. Sweet update.
Whilst Solaris very rarely insists we run fsck, we have had a number
of cases where we have found files corrupted following a crash - even
with UFS journalling enabled. Unfortunately, this isn'
s 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-dis
performance would still
improve. This means you either get better system performance from
the same SSD, or you can get the same system performance from 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
ode. 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@ope
o OS-X would want to
know whether the pool contained resource forks even if opened R/O
but this should not stop a different ZFS 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
lesystem.
BTW, if you do elect to build a bootable, removable drive for backups,
you should be aware that gzip 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 err
CPUs and 2 GB of RAM.
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
o 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
ly 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
3-17.11:17:31 zpool import zroot
2011-03-17.11:30:13 [internal rollback txg: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
d
upgrade your pool to v15 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
Z1 with a
hot spare (7+1+1) is better than 9-way RAIDZ2 (7+2). In the latter
case, your "hot spare" is already part of the pool so you don't
lose the time-to-notice plus time-to-resilver before regaining
redundancy. The downside is that actively using the "hot spar
y "gpart list" - which will display FreeBSD's 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 a
g - 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
oint 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: PG
ailing list 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
>Would I expect to need to reinstall for starters?
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
ome kind 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
have long
>enough lives 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
pgpy
es more RAM). I know my
average blocksize is only a few KB.
--
Peter Jeremy
pgp8Dn2Yb6bMc.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
locked.
>
>
>All 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
pgp1r
isk 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@open
provide support for block sizes other than 512-bytes
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
uot; is at least a clear failure. With a
cheap (or under-dimensioned) PSU, things are more likely to go
out of tolerance under heavy load so you wind up with unrepeatable
strange glitches.
>Think about what happens if you find a silent bit corruption in
>a file system that includes encrypted fi
; 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
pgpOliK2t
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
hancements
it makes to btrfs but there's nothing requiring it to make any further
enhancements at all - it can just walk away from the code.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
ing features
to FreeBSD (or Linux or ...), I'm sure the project would welcome the
assistance.
--
Peter Jeremy
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
leased code 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" 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 no
.
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
meters 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
On 2010-Jul-19 07:15:45 +0800, Richard Elling wrote:
>On Jul 18, 2010, at 3:40 PM, Peter Jeremy wrote:
>> 3.5GB. Note that in any case, patching ARC to work around the out-
>> of-free-memory bug is fairly important.
>
>Do you have a CR for this bug?
This is a FreeBSD-sp
at in any case, patching ARC to work around the out-
of-free-memory bug is fairly important.
>Likewise, how much RAM does OpenSolaris need for stability when running ZFS?
I have a SPARC OSol system that seemed OK with 2GB, though I never really
stres it.
--
Peter Jeremy
pgpXo
e the same
output, please 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
e in some environments. We tend to run equipment into the ground
and I 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.
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
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
a track boundary and and at a cylinder boundary
but I'm not sure if this is a restriction on LBA disks.
Note that if you keep a record of your existing c5d0 format and
restore it later, this will recover your existing boot and swap so you
shouldn't need to restore th
ly possible to extend inodes of files, to
>include parent pointers.
This is a far 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"
started with.
Any user can do this (subject to permissions) and this is how 'pwd'
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
_
I can suggest 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/listinfo/zfs-discuss
ll numbers of links. Then
you will need to patch the vnode operations underlying creat(),
link(), unlink(), rename(), mkdir() 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
is like
pulling teeth but Oracle is far worse - as far as I can tell, 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
fication but may be higher amplitude than
spindle-related vibration.
And finally, there's vibration from the various fans in the case
--
Peter Jeremy
pgpzLzQFwbegr.pgp
Description: PGP signature
___
zfs-discuss mailing list
z
int
where zpool was reporting ~2% free space - and performance was
absolutely abyssmal (fsync() was taking over 16 seconds). When 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
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
s to
be present and a 'zpool scrub' reported no errors. I have reverted
back to Solaris 10 and successfully copied all the data off.
--
Peter Jeremy
pgpC0sjEufK37.pgp
Description: PGP signature
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
rs from a linear 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-discus
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
rotect against failures localized in
>space, but as all 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
disappear.
For that matter:
1) Why is the whole pool faulted when n-2 vdevs are online?
2) Given 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
70 matches
Mail list logo
