I believe this is relevant: http://github.com/pjjw/logfix
Saved my array last year, looks maintained.
On 27/09/2009, at 4:49 AM, Erik Ableson wrote:
Hmmm - this is an annoying one.
I'm currently running an OpenSolaris install (2008.11 upgraded to
2009.06) :
SunOS shemhazai 5.11 snv_111b i86
On 09/26/09 05:57 PM, Toby Thain wrote:
It has long been the default in Gentoo. This system in particular was
installed in 2004.
Not so with Fedora (before C11, anyway) or Red Hat 5. Nothing in FC10
is mapped to tmpfs. Now there's another good reason to use Solaris over
Linux -- consistency ac
Do you have a backup copy of your zpool.cache file?
If you have that file, ZFS will happily mount a pool on boot without its slog
device - it'll just flag the slog as faulted and you can do your normal
replace. I used that for a long while on a test server with a ramdisk slog -
and I never nee
On 26-Sep-09, at 2:55 PM, Frank Middleton wrote:
On 09/26/09 12:11 PM, Toby Thain wrote:
Yes, but unless they fixed it recently (>=RHFC11), Linux doesn't
actually nuke /tmp, which seems to be mapped to disk. One side
effect is that (like MSWindows) AFAIK there isn't a native tmpfs,
...
Are
On 09/26/09 05:25 PM, Ian Collins wrote:
Most of /opt can be relocated
There isn't much in there on a vanilla install (X86 snv111b)
# ls /opt
DTT SUNWmlib
http://www.sun.com/bigadmin/features/articles/nvm_boot.jsp
You pretty much answered the OP with this link. Thanks for
posting it!
Ch
Frank Middleton wrote:
I suppose /var/tmp on zfs would never actually write these files unless
they were written synchronously. In the context of this thread, for
those of us with space constrained boot disks/ssds, is it OK to map
/var/tmp to /tmp, and /var/crash, /var/dump, and swap to a separa
Alas you need the fix for:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4852783
Until that arrives mirror the disk or rebuild the pool.
--chris
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensola
> This controller card, you have turned off any raid functionality, yes? ZFS
> has total control of all discs, by itself? No hw raid intervening?
> --
> This message posted from opensolaris.org
>
>
yes, it's an LSI 150-6, with the BIOS turned off, which turns it into a
dumb SATA card.
Paul
_
On 09/26/09 12:11 PM, Toby Thain wrote:
Yes, but unless they fixed it recently (>=RHFC11), Linux doesn't
actually nuke /tmp, which seems to be mapped to disk. One side
effect is that (like MSWindows) AFAIK there isn't a native tmpfs,
...
Are you sure about that? My Linux systems do.
http://lx
Hmmm - this is an annoying one.
I'm currently running an OpenSolaris install (2008.11 upgraded to 2009.06) :
SunOS shemhazai 5.11 snv_111b i86pc i386 i86pc Solaris
with a zpool made up of one radiz vdev and a small ramdisk based zil. I
usually swap out the zil for a file-based copy when I need
Have you considered bying support? Maybe you will get guaranteed help, then?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On second though, i used zdb -l to show each device - looks like my dd didnt
have the desired effects i wanted.
I'm still showing a newer TGX number for all of my drives except c0t2d0 (the
replacement which they fixed). (This is probably why it wont mount eh?)
Is there anything else i need to
I had a zfs partition written using zfs113 for Mac large around 1.37
TB, then under freebsd 7.2 following a guide on wiki I had wrote 'zpool
create trunk' eventually rewriting the partition. Now the question is
how to recover the partition or to recover data from it? Thanks
___
On 09/25/09 09:58 PM, David Magda wrote:
The contents of /var/tmp can be expected to survive between boots (e.g.,
/var/tmp/vi.recover); /tmp is nuked on power cycles (because it's just
memory/swap):
Yes, but does mapping it to /tmp have any issues regarding booting
or image-update in the conte
Richard Elling wrote:
Assertion failures indicate bugs. You might try another version of the OS.
In general, they are easy to search for in the bugs database. A quick
search reveals
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6822816
but that doesn't look like it will help you. I
Long story short, my cat jumped on my server at my house crashing two drives at
the same time. It was a 7 drive raidz (next time ill do raidz2).
The server crashed complaining about a drive failure, so i rebooted into single
user mode not realizing that two drives failed. I put in a new 500g
Oh, ps, This is on a Solaris 5.11 snv_99 - thanks! liam
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I had this same question. I was recommended to use rsync or zfs send. I used
both just to be safe. With zfs send, you create a snapshot and then send the
snapshot. After deleting the snapshot on the target, you have identical copies.
rsync seems to be used for this task also. And also zfs send.
This controller card, you have turned off any raid functionality, yes? ZFS has
total control of all discs, by itself? No hw raid intervening?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mai
On 26-Sep-09, at 9:56 AM, Frank Middleton wrote:
On 09/25/09 09:58 PM, David Magda wrote:
...
Similar definition for [/tmp] Linux FWIW:
Yes, but unless they fixed it recently (>=RHFC11), Linux doesn't
actually
nuke /tmp, which seems to be mapped to disk. One side effect is
that (like
M
20 matches
Mail list logo
