Re: 6.3 nfe: dead after system reset

On Mon, Oct 20, 2008 at 03:50:21PM +0300, Andriy Gapon wrote: > > Pyun, > > something new about this issue. > Today I got another instance of it, but with a new twist. > In addition to all the usual symptoms I got a lot of messages like the > following in console: > > nfe0: discard fram

Re: constant zfs data corruption

On Mon, 20 Oct 2008, Fabian Keil wrote: > Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > > On Mon, Oct 20, 2008 at 03:07:30PM -0200, JoaoBR wrote: > > > On Monday 20 October 2008 11:22:08 you wrote: > > > > > Also, do you not think it's a little odd that the only data > > > > corruption oc

Re: re0 problem

On Mon, Oct 20, 2008 at 01:28:27PM +0400, Ilya Bakulin wrote: > Just my five cents... > On my laptop (Dell Vostro 1310) I get _periodically_ (not always!) the same > error: > > re0: Ethernet> port 0x5000-0x50ff mem 0xf841-0xf8410fff,0xf840-0xf840 > irq 16 at device 0.0 on pci7

Re: easy way to upgrade from 6.3 to 7.1 (including port packages)

Doug Barton wrote: The generally accepted wisdom (which I am repeating because I agree with it) is that when updating major versions you should: 1. Carefully back up your configuration files and data 2. Do a clean install of the new version 3. Update configuration files 4. Restore data 5. Re-in

Re: Request for testing - top 3.8b1 in the base system

Philip Paeps wrote: On 2008-09-28 14:24:09 (+0200), Nikola Lečić <[EMAIL PROTECTED]> wrote: On Sun, 28 Sep 2008 15:46:20 +1000 Edwin Groothuis <[EMAIL PROTECTED]> wrote: Please report any issues with it (compile time, run time) and a way to reproduce it (if possible). Thanks for your help! las

Re: Process in "uwait" state

On Sunday 19 October 2008 07:17:05 pm Vaclav Haisman wrote: > Hi, > I am trying to compile TrueCrypt 6.0a (The tweaked port source is > available at .), > using Miwi's 5.0 port as base, and everything goes smooth up to the > point where the tru

Re: panic on RELENG_6

On Saturday 18 October 2008 12:13:22 pm Mike Tancsa wrote: > A kernel from Feb 2008 was working just fine > until we updated to a new one on Thursday > > > kgdb kernel.debug /var/crash/vmcore.0 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, cove

Re: constant zfs data corruption

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Chadwick wrote: [snip] > Ahh, I see. So to paraphrase, ZFS can detect checksum errors (data > corruption) using any pool type (single disk, mirror, raidz, whatever), > but can only *repair* the error when using a mirror or raidz. Also when cop

Re: constant zfs data corruption

> all right and understood but shouldn't something as fsck should correct the > error? Seems kind of problematic to me mounting zfs in single user mode, > deleting the file and restarting the OS ? According to Sun's documents, removing corrupted file seems to be 'official' way to get rid of the pr

Re: constant zfs data corruption

Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008 at 03:07:30PM -0200, JoaoBR wrote: > > On Monday 20 October 2008 11:22:08 you wrote: > > > Also, do you not think it's a little odd that the only data > > > corruption occurring for you are related to RRDtool? > > > > this yes I t

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 1:32 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008 at 03:18:01PM -0200, JoaoBR wrote: > > On Monday 20 October 2008 15:03:14 Chuck Swiger wrote: > > > On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: > > > > Hm... I thought we determined earlier i

Re: constant zfs data corruption

On Oct 20, 2008, at 10:19 AM, Jeremy Chadwick wrote: He's not getting working filesystem redundancy with the existing config and is vulnerable to losing data from a single drive failure, agreed. But the ZFS checksum mechanism should still be working to detect data corruption, even though ZFS ca

Re: constant zfs data corruption

JoaoBR <[EMAIL PROTECTED]> wrote: > On Monday 20 October 2008 11:22:08 you wrote: > > On Mon, Oct 20, 2008 at 08:37:40AM -0200, JoaoBR wrote: > > > On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: > > > > On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: > > > > > constantly I find data corruption

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 03:18:01PM -0200, JoaoBR wrote: > On Monday 20 October 2008 15:03:14 Chuck Swiger wrote: > > On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: > > > Hm... I thought we determined earlier in this thread that the OP is > > > not > > > getting the benefits of ZFS checksums be

Re: constant zfs data corruption

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JoaoBR wrote: > On Friday 17 October 2008 15:49:54 Xin LI wrote: [...] >>> some idea? >> For ZFS: I think you need to remove these file. ZFS scrub does not >> recover file if you don't have redundant, e.g. copies=2 or raid-z, etc. > > ok I see, I di

Re: constant zfs data corruption

On Monday 20 October 2008 15:03:14 Chuck Swiger wrote: > On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: > > Hm... I thought we determined earlier in this thread that the OP is > > not > > getting the benefits of ZFS checksums because he's not using raidz > > (only > > a single disk with a sing

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 10:03:14AM -0700, Chuck Swiger wrote: > On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: >> Hm... I thought we determined earlier in this thread that the OP is >> not >> getting the benefits of ZFS checksums because he's not using raidz >> (only >> a single disk with

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 03:07:30PM -0200, JoaoBR wrote: > On Monday 20 October 2008 11:22:08 you wrote: > > On Mon, Oct 20, 2008 at 08:37:40AM -0200, JoaoBR wrote: > > > On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: > > > > On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: > > > > > constantly I

Re: constant zfs data corruption

On Monday 20 October 2008 14:44:50 Chuck Swiger wrote: > Hi, all-- > > On Oct 20, 2008, at 6:22 AM, Jeremy Chadwick wrote: > [ ...JoaoBR wrote... ] > > >> well, hardware seems to be ok and not older than 6 month, also > >> happens not > >> only on one machine ... smartctl do not report any hw failu

Re: constant zfs data corruption

On Monday 20 October 2008 11:22:08 you wrote: > On Mon, Oct 20, 2008 at 08:37:40AM -0200, JoaoBR wrote: > > On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: > > > On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: > > > > constantly I find data corruption on ZFS volums, ever from rrdtool, > > > > th

Re: constant zfs data corruption

On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: Hm... I thought we determined earlier in this thread that the OP is not getting the benefits of ZFS checksums because he's not using raidz (only a single disk with a single pool)? He's not getting working filesystem redundancy with the exi

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 09:44:50AM -0700, Chuck Swiger wrote: > Hi, all-- > > On Oct 20, 2008, at 6:22 AM, Jeremy Chadwick wrote: > [ ...JoaoBR wrote... ] >>> well, hardware seems to be ok and not older than 6 month, also >>> happens not >>> only on one machine ... smartctl do not report any hw f

Re: constant zfs data corruption

Hi, all-- On Oct 20, 2008, at 6:22 AM, Jeremy Chadwick wrote: [ ...JoaoBR wrote... ] well, hardware seems to be ok and not older than 6 month, also happens not only on one machine ... smartctl do not report any hw failures on disk regarding jumpering the drives to 150 you suspect a driver p

FTDI FT232BM USB-COM driver problems

Hi. I have some problems with USB->Serial FTDI FT232BM chip drivers on FreeBSD 7.0... FreeBSD recognize the USB device, but when I making connection to /dev/cuaU0 or /dev/ttyU0 I cant send & receive any data from device. cu -l/dev/cuaU0 -s9600 - No response at all, can't even quit the program cu -

Re: constant zfs data corruption

On Mon, Oct 20, 2008 at 08:37:40AM -0200, JoaoBR wrote: > On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: > > On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: > > > constantly I find data corruption on ZFS volums, ever from rrdtool, > > > this > > > corrupt data happens on SATA disks, never seem

Re: 6.3 nfe: dead after system reset

Pyun, something new about this issue. Today I got another instance of it, but with a new twist. In addition to all the usual symptoms I got a lot of messages like the following in console: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) and even couple like this: nfe0: discard

Re: constant zfs data corruption

On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: > On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: > > constantly I find data corruption on ZFS volums, ever from rrdtool, > > this > > corrupt data happens on SATA disks, never seem on SCSI > > Presumably your SATA drives are correctly being report

Re: constant zfs data corruption

On Friday 17 October 2008 15:49:54 Xin LI wrote: > JoaoBR wrote: > > Hi > > > > constantly I find data corruption on ZFS volums, ever from rrdtool, this > > corrupt data happens on SATA disks, never seem on SCSI > > > > scrub is not able to repair, when comes to touch this files machines > > reboot

Re: SETFEATURES SET TRANSFER MODE taskqueue timeout.. Error occuring constantly.. Please help!!

I have made some changes, and provided requested details. Issue is still occuring, so if it looks like it's going to be more trouble than it's worth I will probably just replace 3 of the PATA IDE disks with a SATA disk and just throw the remaining PATA on the Nvidia ATA controller? Thanks for your

Re: re0 problem

Hi Pyun! > > FreeBSD pelsia.ninth-nine.com 8.0-CURRENT FreeBSD 8.0-CURRENT #28: Sun Oct > 12 21:55:35 JST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PELSIA amd64 > > FreeBSD melfina.ninth-nine.com 8.0-CURRENT FreeBSD 8.0-CURRENT #74: Thu > Aug 28 05:24:38 JST 2008 [EMAIL PROTECTED]:

Re: re0 problem

Just my five cents... On my laptop (Dell Vostro 1310) I get _periodically_ (not always!) the same error: re0: port 0x5000-0x50ff mem 0xf841-0xf8410fff,0xf840-0xf840 irq 16 at device 0.0 on pci7 re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 re0: PHY write failed re0: PHY write

Re: re0 problem

On Mon, Oct 20, 2008 at 01:25:04AM +0900, Norikatsu Shigemura wrote: > Hi Pyun! > > On Sat, 18 Oct 2008 11:02:48 +0900 > Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > > re(4) didn't require special PHY handling for 8169/8110 > > controllers. Did it ever work on older FreeBSD releases? I vaguel