Hello,
Not sure if it's worth troubleshooting this too much before upgrading, but
we recently had an 8.1R/amd64 box hang in a way that suggested everything
was waiting on disk access. It's remote and we had to resort to a
power-cycle to bring it back (we have serial console, but it hung
Portmgr published a new page on their website which describes the
current support and EoL policies for the ports tree and released
packages. The main take-home messages are:
- Support of FreeBSD releases by ports and the ports infrastructure
matches the policies set out by the FreeBSD Security
On Tue, May 17, 2011 at 02:43:44AM -0400, Charles Sprickman wrote:
Not sure if it's worth troubleshooting this too much before
upgrading, but we recently had an 8.1R/amd64 box hang in a way that
suggested everything was waiting on disk access. It's remote and we
had to resort to a power-cycle
on 17/05/2011 10:30 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 02:43:44AM -0400, Charles Sprickman wrote:
Does this sound familiar to anyone running ZFS with snapshots?
Yes, and is exactly why I don't use them. :-)
You put a smiley, but is this an attempt at FUD?
--
On Tue, May 17, 2011 at 01:48:04PM +0300, Andriy Gapon wrote:
on 17/05/2011 10:30 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 02:43:44AM -0400, Charles Sprickman wrote:
Does this sound familiar to anyone running ZFS with snapshots?
Yes, and is exactly why I don't use
on 17/05/2011 14:29 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 01:48:04PM +0300, Andriy Gapon wrote:
on 17/05/2011 10:30 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 02:43:44AM -0400, Charles Sprickman wrote:
Does this sound familiar to anyone running ZFS with
Greetings, dear Sirs
We are using FreeBSD 8.2-RELEASE-p1 as main gateway router at HP DL160
G6 with Intel 82576 integrated network adapter (works fine with MSI-X)
driver version - Intel(R) PRO/1000 Network Connection version - 2.2.3
to get more ports we installed additional network adapter
On Tue, May 17, 2011 at 02:55:54PM +0300, Andriy Gapon wrote:
on 17/05/2011 14:29 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 01:48:04PM +0300, Andriy Gapon wrote:
on 17/05/2011 10:30 Jeremy Chadwick said the following:
On Tue, May 17, 2011 at 02:43:44AM -0400, Charles
on 17/05/2011 15:23 Jeremy Chadwick said the following:
So for Charles' situation, the next time it happens what would be useful
for him to provide? The best I could come up with was to induce doadump
then reboot to get the system up/working again, and then use kgdb
after-the-fact.
This is
On Tue, 17 May 2011, Andriy Gapon wrote:
on 17/05/2011 15:23 Jeremy Chadwick said the following:
So for Charles' situation, the next time it happens what would be useful
for him to provide? The best I could come up with was to induce doadump
then reboot to get the system up/working again, and
on 18/05/2011 04:49 Charles Sprickman said the following:
On Tue, 17 May 2011, Andriy Gapon wrote:
Less drastic approach to hanged I/O debugging is to find out where
processes/threads are actually stuck. E.g. using procstat -kk.
Odd you say that because we've got an old 32-bit 8.1 box
11 matches
Mail list logo
