From owner-freebsd-questions@freebsd.org Sun Jun 28 14:46:05 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4CDD98F46A for ; Sun, 28 Jun 2015 14:46:05 +0000 (UTC) (envelope-from yudi.tux@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70A801E16 for ; Sun, 28 Jun 2015 14:46:05 +0000 (UTC) (envelope-from yudi.tux@gmail.com) Received: by wiwl6 with SMTP id l6so79360550wiw.0 for ; Sun, 28 Jun 2015 07:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MdvU3PDujcBSwPn2inJxEGGQcrzbFgnUa2CF8xcP/F4=; b=jrer1e+P74hksMwOYP7y2AQovK+cmQFDdb0xvByHc3bxOtAuRHYpJuyRkgJqkJV9Oh vlrtfGgNp3ixioMPL+lOSQ4xW9la4M9VzFWaZSRzETiZDNBICP/56hBZdVoA/z2VhRtN TPnxukoR6nLeswv4e4bSzXdyFQRwOsq6OdUzWYFb+46bWs/Sra3a1fEyavNPmMhgQaKf 2tLmL9lMQ6RZNNeRQSfLmmXM6kkwxAuAKnPmHwU9twQ/ZdtccxzIPgcqHeaT4e0uJeBw wKnVW0/izYK8bkJZHsOO/ZeaYOwXFmKYJvZ993TQ3gsfRfA6KHWWMGYMu83LFPJ0ThDq AtcQ== MIME-Version: 1.0 X-Received: by 10.180.106.137 with SMTP id gu9mr14677607wib.54.1435502763621; Sun, 28 Jun 2015 07:46:03 -0700 (PDT) Received: by 10.28.101.67 with HTTP; Sun, 28 Jun 2015 07:46:03 -0700 (PDT) In-Reply-To: <20150628162341.13473f1b.freebsd@edvax.de> References: <20150628144020.e72e3f79.freebsd@edvax.de> <20150628162341.13473f1b.freebsd@edvax.de> Date: Mon, 29 Jun 2015 00:46:03 +1000 Message-ID: Subject: Re: Help fixing a bug; HP MicroServer N40L; CAM status: Command timeout From: Yudi V To: Polytropon Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2015 14:46:06 -0000 > The output of dmesg indicates that the drives are of different > speed capabilities (2 x 300MB/s, 2 x 150MB/s). Are those the > four ones that occupy the 4 cages (and are probably connected > to the same controller)? > 4-bay cage has the 2 Hitachi drives (ada1 and ada0 holds just data in a 2-way mirror on a separate pool) that are on the 3Gbps link and once I sort out this issue I am going to add two more drives to this pool. and the Samsung drives (ada2 and ada3 are on the internal sata port and the eSata link @ 1.5Gbps link in IDE mode) have the OS (again 2-way mirror on a separate pool) > > If you check "dmesg | grep ahci" you can see which controllers > are available. Using "camcontrol devlist" you can examine how > the drives are connected to the available buses. > > output of "dmesg | grep ahci" > ============================= > ahci0: port > 0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f mem > 0xfe6ffc00-0xfe6fffff irq 19 at device 17.0 on pci0 > ahci0: AHCI v1.20 with 4 3Gbps ports, Port Multiplier supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 > ====================================== output of "camcontrol devlist" =================================== at scbus0 target 0 lun 0 (ada0,pass0) at scbus2 target 0 lun 0 (ada1,pass1) at scbus4 target 0 lun 0 (ada2,pass2) at scbus4 target 1 lun 0 (ada3,pass3) ====================================================== > > > > so how to make sure I include the patch? > > Download it and apply it using the "patch" command, for > example "patch < /tmp/the-patch-file". > I will try this and post back later. > > > > I will reread the docs and try rebuilding the kernel again. > > If you have confirmed that v11 works for you, why not use the > current snapshot? It already seems quite stable... > confirmed v11 does not have this issue, I installed it on the same system in a different dataset and it works fine but I am not brave enough to run a developmental version on a file server. I am struggling to fix a single bug and imagine the grief I will have to face if I encounter an issue with v11. -- Kind regards, Yudi