Hello,
I'm running FreeBSD 9.0/amd64, pure ZFS setup, one Seagate disk
ST2000NM0011 SN02 on LSI Logic (mpt) controller.
Yes, I know that running one disk on RAID controller is a bit weird, I
have to find yet if it is possible to connect disk to internal SATA
controller.
About two days
Hello Alex,
SMART values are collected by the disk itself (smartmontools is only
reading it).
This would imply that the problem is between disk and controller.
Since you have tons of Hardware_ECC_Recovered and none of
UDMA_CRC_Error_Count I would think that the problem is with disk
itself.
I
Try running diskinfo -t /dev/...
If it says your device is really slow it's probably dying. I'd suspect it's
having trouble seeking.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
On 22 déc. 2012, at 10:01, Derek Kulinski wrote:
Your drive is 2TB, and according to this the bigger the drive the more
likely you'll run into problems like these:
http://forums.storagereview.com/index.php/topic/27994-smart-hardware-ecc-recovered-values/
Thanks Derek for this interesting
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze:
It looks like the reason for the difference to ipv4_addrs_IF is that
the alias parameter for ifconfig(8) operates differently for IPv6
addresses, the first address of an interface can't be added with
alias, for IPv4 it does not care. I'll have to
Hello!
I've set up several nightly backups all using the pipe-chain of dump |
xz -9 | ccrypt /remote/backups/fs.xz.cpt
On one system these just work every night without a problem. On another
I see xz SEGFAULT-ing about 90% through almost every night for one of
the filesystems (the bigger
On Sat, Dec 22, 2012 at 4:25 PM, Łukasz Wąsikowski
luk...@wasikowski.net wrote:
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze:
It looks like the reason for the difference to ipv4_addrs_IF is that
the alias parameter for ifconfig(8) operates differently for IPv6
addresses, the first address of
Is it dumping core?
Adrian
On 22 December 2012 07:07, Mikhail T. mi+t...@aldan.algebra.com wrote:
Hello!
I've set up several nightly backups all using the pipe-chain of dump | xz -9
| ccrypt /remote/backups/fs.xz.cpt
On one system these just work every night without a problem. On
Quoth =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= luk...@wasikowski.net:
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze:
Yeah, this is problem in network.subr. An interface is not recognized
as IPv6 capable if the interface is not in ipv6_network_interfaces
and there's no ifconfig_IF_ipv6 in
W dniu 2012-12-22 18:14, Ben Morrow pisze:
Quoth =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= luk...@wasikowski.net:
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze:
Yeah, this is problem in network.subr. An interface is not recognized
as IPv6 capable if the interface is not in
On 22.12.2012 11:39, Adrian Chadd wrote:
Is it dumping core?
Yes, and, as I type this, I'm trying to reproduce the crash using the
version of liblzma.so.5 compiled with -O0 -g (under valgrind). So far
(25%) everything is clean and valgrind has no complaints either.
Yours,
-mi
Following
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
e.g.
http://forums.freebsd.org/showthread.php?t=36314
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583.html
Sent from the freebsd-stable mailing
On 12/23/2012 12:27 AM, Jakub Lach wrote:
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
e.g.
http://forums.freebsd.org/showthread.php?t=36314
jup, I can comfirm this with nanobsd (cross) compiled
for my soekris net4501 which has 64 MB mem:
from dmesg:
On 23 December 2012 03:40, Marten Vijn i...@martenvijn.nl wrote:
On 12/23/2012 12:27 AM, Jakub Lach wrote:
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
e.g.
http://forums.freebsd.org/showthread.php?t=36314
jup, I can comfirm this with nanobsd
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
I prepared old laptop for something else and tried live cd
image out.
It took some time to load and I was surprised how slowly it
went. Laptop has 128 mb or ram and might be a bit old to
compare. I removed
On Sun, 23 Dec 2012 03:45:39 +0300, Sergey Kandaurov wrote:
On 23 December 2012 03:40, Marten Vijn i...@martenvijn.nl wrote:
On 12/23/2012 12:27 AM, Jakub Lach wrote:
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
e.g.
Ken,
Does CAM CTL really need to pre-allocate 35MB of RAM at startup?
Adrian
On 22 December 2012 16:45, Sergey Kandaurov pluk...@gmail.com wrote:
On 23 December 2012 03:40, Marten Vijn i...@martenvijn.nl wrote:
On 12/23/2012 12:27 AM, Jakub Lach wrote:
Guys, I've heard about some absurd
Hi guys,
Would someone please file a PR for this? This is a huge unused
allocation of memory for something that honestly likely shouldn't have
been included by default in GENERIC.
I've cc'ed ken on a reply to this. Hopefully after the holidays he can
chime in and figure out what's going on.
Greetings.
I have a Dell R710 with a mfi device (PERC 6/i Integrated) that panics almost
immediately on FreeBSD 9. It works fine on FreeBSD 8.2-RELEASE, but I've now
had it panic in FreeBSD 9.0-STABLE and 9.1-RELEASE.
Output of mfiutil show adapter and panic backtrace below. Anybody seen this
Greetings.
I have a Dell R710 with a mfi device (PERC 6/i Integrated) that panics almost
immediately on FreeBSD 9. It works fine on FreeBSD 8.2-RELEASE, but I've now
had it panic in FreeBSD 9.0-STABLE and 9.1-RELEASE.
Output of mfiutil show adapter and panic backtrace below. Anybody
20 matches
Mail list logo
