<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs">
    <title>gmane.os.solaris.opensolaris.zfs</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51152"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51151"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51150"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51149"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51148"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51147"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51146"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51145"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51144"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51143"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51142"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51141"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51140"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51139"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51138"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51137"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51136"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51135"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51134"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51133"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51152">
    <title>Re: LAST CALL: zfs-discuss is moving Sunday, March 24, 2013</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51152</link>
    <description>&lt;pre&gt;However, the zfs-discuss list seems to be archived at gmane.


On 2013-03-22 22:57, Cindy Swearingen wrote:
&lt;/pre&gt;</description>
    <dc:creator>Hans J. Albertsson</dc:creator>
    <dc:date>2013-03-24T11:03:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51151">
    <title>Dirves going offline in Zpool</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51151</link>
    <description>&lt;pre&gt;Hi,

I have Dell md1200 connected to two heads ( Dell R710 ). The heads have
Perc H800 card and drives are configured in Raid0 ( Virtual Disk) in the
RAID controller.

One of the drives had crashed and is replaced by a spare. Resilvering was
triggered but fails to complete due to drives going offline.  I have to
reboot the head ( R710) and drives comes online. This happened  repeatedly
when resilver was 4% done, and again was rebooted ,  again hung at 27%
done, etc.

The issues happens with both Solaris11.1/ Omnios.
Its a 100Tb  pool with 69Tb used. I have critical data and cant afford loss
of data.
Can I recover the data anyway ( atleast partially ) ?

I had verified there is no hardware issue with H800 and also upgraded the
firmware for H800. The issue happens with both the heads.

Current OS: Solaris 11.1

Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci&amp;lt; at &amp;gt;0
,0/pci8086,340e&amp;lt; at &amp;gt;7/pci1028,1f15&amp;lt; at &amp;gt;0/sd&amp;lt; at &amp;gt;12,0 (sd26):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:4&lt;/pre&gt;</description>
    <dc:creator>Ram Chander</dc:creator>
    <dc:date>2013-03-23T07:59:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51150">
    <title>LAST CALL: zfs-discuss is moving Sunday, March 24,2013</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51150</link>
    <description>&lt;pre&gt;I hope to see everyone on the other side...

***************************************

The ZFS discussion list is moving to java.net.

This opensolaris/zfs discussion will not be available after March 24.
There is no way to migrate the existing list to the new list.

The solaris-zfs project is here:

http://java.net/projects/solaris-zfs

See the steps below to join the ZFS project or just the discussion list,
but you must create an account on java.net to join the list.

Thanks, Cindy

1. Create an account on java.net.

https://java.net/people/new

2. When logged in to your java.net account, join the solaris-zfs
project as an Observer by clicking the Join This Project link on the
left side of this page:

http://java.net/projects/solaris-zfs

3. Subscribe to the zfs discussion mailing list here:

http://java.net/projects/solaris-zfs/lists
&lt;/pre&gt;</description>
    <dc:creator>Cindy Swearingen</dc:creator>
    <dc:date>2013-03-22T21:57:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51149">
    <title>How to enforce probing of all disks?</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51149</link>
    <description>&lt;pre&gt;Hello all,

   I have a kind of lame question here: how can I force the system (OI)
to probe all the HDD controllers and disks that it can find, and be
certain that it has searched everywhere for disks?

   My remotely supported home-NAS PC was unavailable for a while, and
a friend rebooted it for me from a LiveUSB image with SSH (oi_148a).
I can see my main pool disks, but not the old boot (rpool) drive.
Meaning, that it does not appear in "zpool import" nor in "format"
outputs. While it is possible that it has finally kicked the bucket,
and that won't really be unexpected, I'd like to try and confirm.

   For example, it might fail to spin up or come into contact with
the SATA cable initially - but subsequent probing of the same
controller might just find it. Happened before, too - though
via a reboot and full POST... The friend won't be available for a
few days, and there's no other remote management nor inspection
facility for this box, so I'd like to probe from within OI as much
as I can. Should be an e&lt;/pre&gt;</description>
    <dc:creator>Jim Klimov</dc:creator>
    <dc:date>2013-03-22T15:20:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51148">
    <title>Re: SSD for L2arc</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51148</link>
    <description>&lt;pre&gt;
The "man zpool" page is quite informative on theory and concepts ;)

If your pool already exists, you can prepare the SSD (partition/slice
it) and:
# zpool add POOLNAME cache cXtYdZsS

Likewise, to add a ZIL device you can add a "log" device, either as
a single disk (slice) or as a mirror of two or more:
# zpool add POOLNAME log cXtYdZsS
# zpool add POOLNAME log mirror cXtYdZsS1 cXtYdZsS2



It may increase performance in two ways:

If you have any apps (including NFS, maybe VMs, iSCSI, etc. - not only
databases) that regularly issue "synchronous" writes - those which must
be stored on media (not just cached and queued) before the call returns
a success, then the ZIL catches these writes instead of the main pool
devices. The ZIL is written as ring buffer, so its size is proportional
to your pool's throughput - about 3 full-size TXG syncs should fit into
the designated ZIL space. That's usually max bandwidth (X Mb/s) times
15 sec (3*5s), or a bit more for peace of mind.

1) If the ZIL device (SLOG) is an SSD&lt;/pre&gt;</description>
    <dc:creator>Jim Klimov</dc:creator>
    <dc:date>2013-03-21T18:05:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51147">
    <title>Re: SSD for L2arc</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51147</link>
    <description>&lt;pre&gt;

Read the documentation, specifically the section titled;

Creating a ZFS Storage PoolWith Cache Devices



That is not correct - the ZIL is used for synchronous writes.

From the documentation:

The ZFS intent log (ZIL) is provided to satisfy POSIX requirements for synchronous
transactions. For example, databases often require their transactions to be on stable storage
devices when returning from a system call. NFS and other applications can also use fsync() to
ensure data stability.

By default, the ZIL is allocated from blocks within the main pool.However, better performance
might be possible by using separate intent log devices, such asNVRAMor a dedicated disk.



_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Jim Mauro</dc:creator>
    <dc:date>2013-03-21T15:50:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51146">
    <title>SSD for L2arc</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51146</link>
    <description>&lt;pre&gt;Hi,

Can I know how to configure a SSD to be used for L2arc ? Basically I want
to improve read performance.
To increase write performance, will SSD for Zil help ? As I read on forums,
Zil is only used for mysql/transaction based writes. I have regular writes
only.

Thanks.

Regards,
Ram
_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Ram Chander</dc:creator>
    <dc:date>2013-03-21T15:24:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51145">
    <title>Re: This mailing list EOL???</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51145</link>
    <description>&lt;pre&gt;mail-archive.com is an independent third party.

This is one of their FAQ's
http://www.mail-archive.com/faq.html#duration

The Mail Archive has been running since 1998. Archiving services are planned to continue indefinitely. We do not plan on ever needing to remove archived material. Do not, however, misconstrue these intentions with a warranty of any kind. We reserve the right to discontinue service at any time.



From: zfs-discuss-bounces&amp;lt; at &amp;gt;opensolaris.org [mailto:zfs-discuss-bounces&amp;lt; at &amp;gt;opensolaris.org] On Behalf Of Deirdre Straughan
Sent: Wednesday, March 20, 2013 5:16 PM
To: Cindy Swearingen; zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
Subject: Re: [zfs-discuss] This mailing list EOL???

Will the archives of all the lists be preserved? I don't think we've seen a clear answer on that (it's possible you haven't, either!).
On Wed, Mar 20, 2013 at 2:14 PM, Cindy Swearingen &amp;lt;cindy.swearingen&amp;lt; at &amp;gt;oracle.com&amp;lt;mailto:cindy.swearingen&amp;lt; at &amp;gt;oracle.com&amp;gt;&amp;gt; wrote:
Hi Ned,

This list is migrating to java.net&amp;lt;http://java.net&amp;gt; and will not be availa&lt;/pre&gt;</description>
    <dc:creator>Edward Ned Harvey (opensolarisisdeadlongliveopensolaris</dc:creator>
    <dc:date>2013-03-21T11:07:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51144">
    <title>Please join us on the new zfs discuss list on java.net</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51144</link>
    <description>&lt;pre&gt;Hi Everyone,

The ZFS discussion list is moving to java.net.

This opensolaris/zfs discussion will not be available after March 24.
There is no way to migrate the existing list to the new list.

The solaris-zfs project is here:

http://java.net/projects/solaris-zfs

See the steps below to join the ZFS project or just the discussion list,
but you must create an account on java.net to join the list.

Thanks, Cindy

1. Create an account on java.net.

https://java.net/people/new

2. When logged in to your java.net account, join the solaris-zfs
project as an Observer by clicking the Join This Project link on the
left side of this page:

http://java.net/projects/solaris-zfs

3. Subscribe to the zfs discussion mailing list here:

http://java.net/projects/solaris-zfs/lists
&lt;/pre&gt;</description>
    <dc:creator>Cindy Swearingen</dc:creator>
    <dc:date>2013-03-21T00:14:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51143">
    <title>Re: System started crashing hard after zpoolreconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51143</link>
    <description>&lt;pre&gt;I can reproduce the problem. I can crash the system.

Here are the steps I did (some steps may not be needed but I haven't tested
it):

- Clean install of OI 151.a.7 on Supermicro hardware described above (32GB
RAM though, not the 128GB)

- Create 1 zpool, 6 raidz vdevs with 5 drives each

- NFS export a dataset
  zfs set sharenfs="rw=&amp;lt; at &amp;gt;10.20.1/24" vol01/htmlspace

- Create zfs child dataset
  zfs create vol01/htmlspace/A

  $ zfs get -H sharenfs vol01/htmlspace/A
  vol01/htmlspace/A       sharenfs        rw=&amp;lt; at &amp;gt;10.20.1/24  inherited from
vol01/htmlspace

- Stop NFS shearing for the child dataset

  zfs set sharenfs=off vol01/htmlspace/A

The crash is instant after the sharenfs=off command.

I thought it was coincident so after reboot I tried it on another dataset.
Instant crash again. I get my prompt back but that's it. The system is gone
after that.

The NFS exported file systems are not accessed by any system on the
network. They are not in use. That's why I wanted to stop exporting them.
And, even if they we&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T21:34:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51142">
    <title>Re: This mailing list EOL???</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51142</link>
    <description>&lt;pre&gt;Will the archives of all the lists be preserved? I don't think we've seen a
clear answer on that (it's possible you haven't, either!).

On Wed, Mar 20, 2013 at 2:14 PM, Cindy Swearingen &amp;lt;
cindy.swearingen&amp;lt; at &amp;gt;oracle.com&amp;gt; wrote:




&lt;/pre&gt;</description>
    <dc:creator>Deirdre Straughan</dc:creator>
    <dc:date>2013-03-20T21:15:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51141">
    <title>Re: This mailing list EOL???</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51141</link>
    <description>&lt;pre&gt;Hi Ned,

This list is migrating to java.net and will not be available
in its current form after March 24, 2013.

The archive of this list is available here:

http://www.mail-archive.com/zfs-discuss&amp;lt; at &amp;gt;opensolaris.org/

I will provide an invitation to the new list shortly.

Thanks for your patience.

Cindy

On 03/20/13 15:05, Edward Ned Harvey 
(opensolarisisdeadlongliveopensolaris) wrote:
&lt;/pre&gt;</description>
    <dc:creator>Cindy Swearingen</dc:creator>
    <dc:date>2013-03-20T21:14:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51140">
    <title>This mailing list EOL???</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51140</link>
    <description>&lt;pre&gt;I can't seem to find any factual indication that opensolaris.org mailing lists are going away, and I can't even find the reference to whoever said it was EOL in a few weeks ... a few weeks ago.

So ... are these mailing lists going bye-bye?
_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Edward Ned Harvey (opensolarisisdeadlongliveopensolaris</dc:creator>
    <dc:date>2013-03-20T21:05:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51139">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51139</link>
    <description>&lt;pre&gt;Great write up Jens.

The chance of two MB to be broken is probably low but overheating is a very
good point. It was on my to-do list to setup IPMI and seems that now is the
best time to do it.

Thanks

On Wed, Mar 20, 2013 at 1:08 PM, Jens Elkner &amp;lt;jel+zfs&amp;lt; at &amp;gt;cs.uni-magdeburg.de&amp;gt;wrote:

_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T20:45:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51138">
    <title>Re: System started crashing hard after zpoolreconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51138</link>
    <description>&lt;pre&gt;
You definitely should! Plugin a cable into the dedicated network port 
and configure it (easiest way for you is probably to jump into the BIOS
and assign the appropriate IP address etc.). Than, for a quick look, 
point your browser to the given IP port 80 (default login is
ADMIN/ADMIN). Also you may now configure some other details
(accounts/passwords/roles).

To track the problem, either write a script, which polls the parameters
in question periodically or just install the latest ipmiViewer and use
this to monitor your sensors ad hoc.
see ftp://ftp.supermicro.com/utility/IPMIView/


Latest LSI FW should be P15, for this MB type 217 (2.17), MB-BIOS C28 (1.0b).
However, I doubt, that your problem has anything to do with the
SAS-ctrl or OI or ZFS.

My guess is, that either your MB is broken (we had an X9DRH-iF, which
instantly "disappeared" as soon as it got some real load) or you have
a heat problem (watch you cpu temp e.g. via ipmiviewer). With 2GHz
that's not very likely, but worth a try (socket placement&lt;/pre&gt;</description>
    <dc:creator>Jens Elkner</dc:creator>
    <dc:date>2013-03-20T20:08:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51137">
    <title>Re: [BULK] System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51137</link>
    <description>&lt;pre&gt;No problem Trey. Anything will help.

Yes, I did a clean install overwriting the old OS.



_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T19:42:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51136">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51136</link>
    <description>&lt;pre&gt;Hi Jim,

Thanks for the pointers. I'll definitely look into this.


--
Peter Blajev
IT Manager, TAAZ Inc.
Office: 858-597-0512 x125


On Wed, Mar 20, 2013 at 11:29 AM, Jim Klimov &amp;lt;jimklimov&amp;lt; at &amp;gt;cos.ru&amp;gt; wrote:

_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T19:38:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51135">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51135</link>
    <description>&lt;pre&gt;
Typically the kernel crash dumps are created as a result of kernel
panic; also they may be forced by administrative actions like NMI.
They require you to configure a dump volume of sufficient size (see
dumpadm) and a /var/crash which may be a dataset on a large enough
pool - after the reboot the dump data will be migrated there.

To "help" with the hangs you can try the BIOS watchdog (which would
require a bmc driver, one which is known from OpenSolaris is alas
not opensourced and not redistributable), or with a software deadman
timer:

http://www.cuddletech.com/blog/pivot/entry.php?id=1044

http://wiki.illumos.org/display/illumos/System+Hangs

Also, if you configure "crash dump on NMI" and set up your IPMI card,
then you can likely gain remote access to both the server console
("physical" and/or serial) and may be able to trigger the NMI, too.

HTH,
//Jim

&lt;/pre&gt;</description>
    <dc:creator>Jim Klimov</dc:creator>
    <dc:date>2013-03-20T18:29:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51134">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51134</link>
    <description>&lt;pre&gt;I'm going to need some help with the crash dumps. I'm not very familiar
with Solaris.

Do I have to enable something to get the crash dumps? Where should I look
for them?

Thanks for the help.


On Wed, Mar 20, 2013 at 8:53 AM, Michael Schuster &amp;lt;michaelsprivate&amp;lt; at &amp;gt;gmail.com

_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T16:15:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51133">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51133</link>
    <description>&lt;pre&gt;How about crash dumps?

michael

On Wed, Mar 20, 2013 at 4:50 PM, Peter Wood &amp;lt;peterwood.sd&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Michael Schuster</dc:creator>
    <dc:date>2013-03-20T15:53:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51132">
    <title>Re: System started crashing hard after zpool reconfigure and OI upgrade</title>
    <link>http://permalink.gmane.org/gmane.os.solaris.opensolaris.zfs/51132</link>
    <description>&lt;pre&gt;I'm sorry. I should have mentioned it that I can't find any errors in the
logs. The last entry in /var/adm/messages is that I removed the keyboard
after the last reboot and then it shows the new boot up messages when I
boot up the system after the crash. The BIOS log is empty. I'm not sure how
to check the IPMI but IPMI is not configured and I'm not using it.

Just another observation - the crashes are more intense the more data the
system serves (NFS).

I'm looking into FRMW upgrades for the LSI now.


On Wed, Mar 20, 2013 at 8:40 AM, Will Murnane &amp;lt;will.murnane&amp;lt; at &amp;gt;gmail.com&amp;gt;wrote:

_______________________________________________
zfs-discuss mailing list
zfs-discuss&amp;lt; at &amp;gt;opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
&lt;/pre&gt;</description>
    <dc:creator>Peter Wood</dc:creator>
    <dc:date>2013-03-20T15:50:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.os.solaris.opensolaris.zfs">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.os.solaris.opensolaris.zfs</link>
  </textinput>
</rdf:RDF>
