From owner-freebsd-fs@freebsd.org Sun Jan 13 15:53:26 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D590F149FCB4 for ; Sun, 13 Jan 2019 15:53:25 +0000 (UTC) (envelope-from info@webskill.online) Received: from mail.webskill.online (webskill.online [103.39.133.70]) by mx1.freebsd.org (Postfix) with ESMTP id C705A82654 for ; Sun, 13 Jan 2019 15:53:22 +0000 (UTC) (envelope-from info@webskill.online) Received: from vaiop8d47dbd68 ([182.75.24.157]) by webskill.online with MailEnable ESMTP; Sun, 13 Jan 2019 17:35:07 +0530 From: To: Subject: Web Optimization Date: Sun, 13 Jan 2019 17:31:50 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AdSrN5VdsL6AM1yETAGfVDIZ9+E8BQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Message-ID: <14B14438B8734DC0999B68AC6A64E43E.MAI@webskill.online> X-Rspamd-Queue-Id: C705A82654 X-Spamd-Bar: ++++++++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [10.32 / 15.00]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[cached: mail.webskill.online]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[157.24.75.182.zen.spamhaus.org : 127.0.0.11]; MIME_TRACE(0.00)[0:+,1:+]; INTRODUCTION(2.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:132779, ipnet:103.39.133.0/24, country:IN]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(3.00)[157.24.75.182.zen.spamhaus.org : 127.0.0.4]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.99)[0.988,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[webskill.online]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE(1.29)[ip: (3.59), ipnet: 103.39.133.0/24(1.54), asn: 132779(1.29), country: IN(0.03)]; NEURAL_SPAM_LONG(1.00)[1.000,0]; FROM_NO_DN(0.00)[]; R_SPF_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[70.133.39.103.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2]; GREYLIST(0.00)[pass,body] X-Spam: Yes Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 15:53:26 -0000 Hi, Hope you are doing well. My name is Sophia and I work for a Search Marketing company. I was doing some research on your industry and see your website. Thing is I had a look at some of the other businesses who are currently ranked on Page 1 and I truly believe you have a better website and a better brand and we can make better position on web for you. Long story short, I have created a Web-Page Analysis of Your Website which addresses all of the technical and web errors on your website. I am happy to send you this Web Page Analysis of Your Website FREE. All I want is the opportunity to call you and discuss for your website in greater detail. What do you think? Can we schedule an meeting with you or can call you? Kind Regards, Sophia From owner-freebsd-fs@freebsd.org Sun Jan 13 11:56:21 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F2B01496539 for ; Sun, 13 Jan 2019 11:56:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EDCC4708E8 for ; Sun, 13 Jan 2019 11:56:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B1AA01496538; Sun, 13 Jan 2019 11:56:20 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76CEC1496537 for ; Sun, 13 Jan 2019 11:56:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1438D708E5 for ; Sun, 13 Jan 2019 11:56:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 43CF5514A for ; Sun, 13 Jan 2019 11:56:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DBuJDU040864 for ; Sun, 13 Jan 2019 11:56:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DBuJmB040863 for fs@FreeBSD.org; Sun, 13 Jan 2019 11:56:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 11:56:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: johanvz816@giantfoo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 11:56:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #12 from johan van Zanten --- (In reply to Conrad Meyer from comment #10) Thank you for checking into this! root file system (SSD): dejacque:~ # tunefs -p /dev/ada0p2 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time /u (data) file system, USB connected HD: dejacque:~ # tunefs -p /dev/da0p4 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L)=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 I'll give memtest86 a shot. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 13 21:00:08 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8ED6C148720D for ; Sun, 13 Jan 2019 21:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 24ADB90C50 for ; Sun, 13 Jan 2019 21:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id DB30A14871FB; Sun, 13 Jan 2019 21:00:07 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B76FC14871FA for ; Sun, 13 Jan 2019 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A47790C4C for ; Sun, 13 Jan 2019 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 83C129FA6 for ; Sun, 13 Jan 2019 21:00:06 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DL06u0091227 for ; Sun, 13 Jan 2019 21:00:06 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DL06Dt091220 for fs@FreeBSD.org; Sun, 13 Jan 2019 21:00:06 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201901132100.x0DL06Dt091220@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 13 Jan 2019 21:00:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 21:00:08 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun Jan 13 21:19:33 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23F7A1488F14 for ; Sun, 13 Jan 2019 21:19:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AF03892322 for ; Sun, 13 Jan 2019 21:19:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 700FA1488F13; Sun, 13 Jan 2019 21:19:32 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D6FB1488F11 for ; Sun, 13 Jan 2019 21:19:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAEFD92320 for ; Sun, 13 Jan 2019 21:19:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 09E62A374 for ; Sun, 13 Jan 2019 21:19:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DLJUQi094851 for ; Sun, 13 Jan 2019 21:19:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DLJUSw094844 for fs@FreeBSD.org; Sun, 13 Jan 2019 21:19:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 21:19:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: johanvz816@giantfoo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 21:19:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #13 from johan van Zanten --- regarding the memory testing: =3D memtest86+ -- my laptop can't boot the ISO image on a USB stick ; maybe= a UEFI compat problem. I installed the memtest86+ package and tried to boot = from the FreeBSD menu (unload ; load /boot/opt/memtest86+). As soon as i hit return, i get a black screen, and then the machine immediately reboots with= out doing any work. =3D memtester -- i ran three instances concurrently to test 6.83 GB of the = 8 GB of RAM (any more RAM and the OS started paging). After four loops, no erro= rs were found. Given that i wasn't have any problems using this same config as a desktop running FreeBSD 10 or 11, with the same sort of workload, it seems less lik= ely that RAM is the problem. Lines 11214 to 11234 from /usr/src/sys/ufs/ffs/ffs_softdep.c: /* * If we have reached the end of the current list without * finding the just finished dependency, then it must be * on the future dependency list. Future dependencies cannot * be freed until they are moved to the current list. */ if (listadp =3D=3D NULL) { #ifdef DEBUG if (adp->ad_state & EXTDATA) listhead =3D &inodedep->id_newextupdt; else listhead =3D &inodedep->id_newinoupdt; TAILQ_FOREACH(listadp, listhead, ad_next) /* found our block */ if (listadp =3D=3D adp) break; if (listadp =3D=3D NULL) panic("handle_allocdirect_partdone: lost dep"); #endif /* DEBUG */ return; } --- That matches the panic sting from Wed Jan 9 23:41:29 CET 2019, but assuming that's where the system is panicking, one still needs to find out how the system is arriving in that state. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 13 23:08:55 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA906148C1F6 for ; Sun, 13 Jan 2019 23:08:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 42F6295A1F for ; Sun, 13 Jan 2019 23:08:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0466B148C1F4; Sun, 13 Jan 2019 23:08:55 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4DE5148C1F2 for ; Sun, 13 Jan 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7454795A1E for ; Sun, 13 Jan 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id ABAC2B37C for ; Sun, 13 Jan 2019 23:08:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DN8rSQ028321 for ; Sun, 13 Jan 2019 23:08:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DN8rNb028320 for fs@FreeBSD.org; Sun, 13 Jan 2019 23:08:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 23:08:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 23:08:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #14 from Conrad Meyer --- (In reply to johan van Zanten from comment #13) > memtest86+ -- my laptop can't boot the ISO image on a USB stick ; maybe a= UEFI compat problem Yeah, memtest86+ is legacy BIOS only :-(. > Given that i wasn't have any problems using this same config as a desktop > running FreeBSD 10 or 11, with the same sort of workload, it seems less l= ikely > that RAM is the problem. Sure. > That matches the panic sting from Wed Jan 9 23:41:29 CET 2019, but assum= ing > that's where the system is panicking, one still needs to find out how the > system is arriving in that state. Yes, that's definitely the panic. The latter is the open question :-). One thing that landed in 12 for UFS was TRIM consolidation, which does inte= ract with softupdates and could plausibly explain this. You have trim enabled on ada0p2 (root) but not the other disk. You could try either disabling consolidation (sysctl vfs.ffs.dotrimcons=3D0) or disabling TRIM on the file= system (tunefs -t disable /dev/ada0p2). Also, kib did some softdep refactoring in 327722 and 327723; Kirk did somet= hing in this area back in 2016 in r304239. I don't know what if any of that was already backported to 11.x and landed in 11.2 or whatever. I'm not sure about the secondary panic. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 13 23:28:27 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CAC3148C7A8 for ; Sun, 13 Jan 2019 23:28:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C8B9E9623F for ; Sun, 13 Jan 2019 23:28:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 892CA148C7A4; Sun, 13 Jan 2019 23:28:26 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 775D6148C7A3 for ; Sun, 13 Jan 2019 23:28:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FBF896237 for ; Sun, 13 Jan 2019 23:28:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 55021B668 for ; Sun, 13 Jan 2019 23:28:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DNSP46068652 for ; Sun, 13 Jan 2019 23:28:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DNSPtd068649 for fs@FreeBSD.org; Sun, 13 Jan 2019 23:28:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 23:28:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 23:28:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 Kirk McKusick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckusick@FreeBSD.org --- Comment #15 from Kirk McKusick --- (In reply to Conrad Meyer from comment #14) Just catching up on recently reported bugs. Thanks for working on tracking this down. Your suggestion on turning off TRIM consolidation is a good one. My 2016 change, -r304239 was to fix softdep roll-forward after transient wr= ite failure. It was MFC'ed to 10-stable and 11-stable on 17-October-2016 so is = not likely to be the cause of this bug. kib's 2018 changes, -r327722 and -r327723 were to fix some missing locking issues. They were MFC'ed to 11-stable on 16-January-2018. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 13 23:56:16 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 240E2148D20A for ; Sun, 13 Jan 2019 23:56:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9BBF69727D for ; Sun, 13 Jan 2019 23:56:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5F2BD148D209; Sun, 13 Jan 2019 23:56:15 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CBAE148D208 for ; Sun, 13 Jan 2019 23:56:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D0CCA9727B for ; Sun, 13 Jan 2019 23:56:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F403ABABD for ; Sun, 13 Jan 2019 23:56:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DNuDLr027829 for ; Sun, 13 Jan 2019 23:56:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DNuDKr027828 for fs@FreeBSD.org; Sun, 13 Jan 2019 23:56:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 23:56:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 23:56:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #16 from Conrad Meyer --- Re secondary panic, we drop UMP lock around setup_inomapdep, but that shoul= d be ok because we still hold the CG buf exclusively -- no one else should be ab= le to allocate the same inode number. I think the panic could be explained by the inode being allocated but unreferenced in the CG bitmap. Possibly due to violation of ordering constraints implied by the first panic =E2=80=94 e.g., inode and directory = entry written, but CG bitmap stale. Or perhaps dirent is stale. Or possibly due= to write-cache enabled disk (which is another way SU ordering constraints can = be violated). But the handle_written_bmsafemap <-> softdep_setup_inomapdep li= nk is suspicious to me and I suspect they are directly related. I would guess CG bitmap accuracy is enforced for non-SU filesystems by a mo= re thorough fsck on dirty mount, but might be mistaken. On non-SU we would not hit this panic because the inodedep would not exist, of course. But we wou= ld hit 'ffs_valloc: dup alloc' shortly afterwards when we noticed the dinode w= as already initialized. Either way, (as far as I can tell) path lookup does not confirm that an ino= de referred to by a directory entry is actually allocated in the CG bitmap. I= t is simply assumed to be consistent. So you might have an active UFS vnode with that inode number with inodedeps for a variety of reasons, and some thread comes along and tries to create a file; that number is free in the CG bitma= p, so the second thread acquires it; and then the creating thread collides with the existing softdep work. I don't know of a good way to fix the secondary panic. A good next step would be to determine if your drives have write caching disabled, and if the drive model is known to respect that bit or not. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 13 23:57:23 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9506148D46C for ; Sun, 13 Jan 2019 23:57:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 84936972E8 for ; Sun, 13 Jan 2019 23:57:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 48039148D468; Sun, 13 Jan 2019 23:57:22 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34EB7148D463 for ; Sun, 13 Jan 2019 23:57:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C494C972E3 for ; Sun, 13 Jan 2019 23:57:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 26AA0BAC1 for ; Sun, 13 Jan 2019 23:57:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0DNvLAB028937 for ; Sun, 13 Jan 2019 23:57:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0DNvLDn028936 for fs@FreeBSD.org; Sun, 13 Jan 2019 23:57:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Sun, 13 Jan 2019 23:57:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 23:57:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #17 from Conrad Meyer --- (In reply to Kirk McKusick from comment #15) Thanks! The MFC history helps narrow down the scope of suspect SU changes = (if it is a new regression). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 14 17:30:17 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B333148124B for ; Mon, 14 Jan 2019 17:30:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 25F236CEFF for ; Mon, 14 Jan 2019 17:30:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DE1771481248; Mon, 14 Jan 2019 17:30:16 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCA991481247 for ; Mon, 14 Jan 2019 17:30:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 662226CEF7 for ; Mon, 14 Jan 2019 17:30:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B25E215633 for ; Mon, 14 Jan 2019 17:30:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0EHUFhW094447 for ; Mon, 14 Jan 2019 17:30:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0EHUFhY094446 for fs@FreeBSD.org; Mon, 14 Jan 2019 17:30:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Mon, 14 Jan 2019 17:30:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maxim.usatov@bcsatellite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 17:30:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 Maxim Usatov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxim.usatov@bcsatellite.ne | |t --- Comment #4 from Maxim Usatov --- I have exactly the same occurring with FreeBSD installed on an SSD. After simulating power outages, the system refuses boot. Booting into single user mode and trying fsck ends with "fsck_ufs: Directory 1284157 name not found"= .=20 This is FreeBSD 10.3-RELEASE-p12. The SSD is mSATA iSLC unit. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 14 17:54:38 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 817C51481E59 for ; Mon, 14 Jan 2019 17:54:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1BEC46E194 for ; Mon, 14 Jan 2019 17:54:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D09771481E58; Mon, 14 Jan 2019 17:54:37 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BED871481E57 for ; Mon, 14 Jan 2019 17:54:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D5B36E191 for ; Mon, 14 Jan 2019 17:54:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6EDDF15A8C for ; Mon, 14 Jan 2019 17:54:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0EHsa4Y046577 for ; Mon, 14 Jan 2019 17:54:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0EHsauA046576 for fs@FreeBSD.org; Mon, 14 Jan 2019 17:54:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Mon, 14 Jan 2019 17:54:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: karl@denninger.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 17:54:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 karl@denninger.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@denninger.net --- Comment #5 from karl@denninger.net --- (In reply to Maxim Usatov from comment #4) A non-power protected SSD typically lies about whether it has actually committed changes to stable storage for reasons of performance. As such the kernel has no idea what is and isn't there. Your issue is likely unrelated; there's no solution to what you're experien= cing other than "don't do that" (meaning either put in a SSD that has power protection or don't unexpectedly kill the power to it.) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 14 18:26:45 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 878A81482EFC for ; Mon, 14 Jan 2019 18:26:45 +0000 (UTC) (envelope-from hello@webskill.online) Received: from mail.webskill.online (webskill.online [103.39.133.70]) by mx1.freebsd.org (Postfix) with ESMTP id 36DE26F4C1 for ; Mon, 14 Jan 2019 18:26:43 +0000 (UTC) (envelope-from hello@webskill.online) Received: from vaiop8d47dbd68 ([182.75.24.157]) by webskill.online with MailEnable ESMTP; Mon, 14 Jan 2019 21:32:32 +0530 From: To: Subject: Re:Web Optimization Date: Mon, 14 Jan 2019 21:31:27 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AdSsG6ZdYjvS1EgUQVm9UMvsqSmEGg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Message-ID: X-Rspamd-Queue-Id: 36DE26F4C1 X-Spamd-Bar: +++++++++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [11.74 / 15.00]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[cached: mail.webskill.online]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[157.24.75.182.zen.spamhaus.org : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:132779, ipnet:103.39.133.0/24, country:IN]; INTRODUCTION(2.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; RECEIVED_SPAMHAUS_XBL(3.00)[157.24.75.182.zen.spamhaus.org : 127.0.0.4]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(1.00)[0.999,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(1.35)[ip: (3.78), ipnet: 103.39.133.0/24(1.61), asn: 132779(1.34), country: IN(0.03)]; DMARC_NA(0.00)[webskill.online]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.40)[5]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; NEURAL_SPAM_LONG(1.00)[1.000,0]; FROM_NO_DN(0.00)[]; R_SPF_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[70.133.39.103.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2]; GREYLIST(0.00)[pass,body] X-Spam: Yes Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 18:26:45 -0000 Hello, I recently sent you an email about Web Optimization. Let me know if you are interested and we can discuss this further. I look forward to your response. Kind Regards, Sophia _____ From: info@webskill.online [mailto:info@webskill.online] Sent: Sunday, January 13, 2019 4:24 PM To: freebsd-fs@freebsd.org Subject: Web Optimization Hi, Hope you are doing well. My name is Sophia and I work for a Search Marketing company. I was doing some research on your industry and see your website. Thing is I had a look at some of the other businesses who are currently ranked on Page 1 and I truly believe you have a better website and a better brand and we can make better position on web for you. Long story short, I have created a Web-Page Analysis of Your Website which addresses all of the technical and web errors on your website. I am happy to send you this Web Page Analysis of Your Website FREE. All I want is the opportunity to call you and discuss for your website in greater detail. What do you think? Can we schedule an meeting with you or can call you? Kind Regards, Sophia From owner-freebsd-fs@freebsd.org Mon Jan 14 18:31:32 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C10261483133 for ; Mon, 14 Jan 2019 18:31:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5DF6F8D4 for ; Mon, 14 Jan 2019 18:31:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EEDCC1483132; Mon, 14 Jan 2019 18:31:31 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD26F1483131 for ; Mon, 14 Jan 2019 18:31:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D8C66F8CB for ; Mon, 14 Jan 2019 18:31:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C024D16042 for ; Mon, 14 Jan 2019 18:31:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0EIVUZR029590 for ; Mon, 14 Jan 2019 18:31:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0EIVUMc029589 for fs@FreeBSD.org; Mon, 14 Jan 2019 18:31:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Mon, 14 Jan 2019 18:31:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 18:31:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 --- Comment #6 from Conrad Meyer --- (In reply to karl from comment #5) On some devices it may be possible to disable volatile write cache, if any.= =20 This is necessary for correct UFS power-fail recovery. (Some disks also lie about allowing write-cache disabled, which is extra fun.) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 14 18:56:54 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AD5D1483FCE for ; Mon, 14 Jan 2019 18:56:54 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4C6B709FE for ; Mon, 14 Jan 2019 18:56:52 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-ua1-x930.google.com with SMTP id e16so15444uam.12 for ; Mon, 14 Jan 2019 10:56:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=KULufWgLJR51+HtB9oZN9XD+CufRM+VC+UW+GVssFLM=; b=YSohpUZdG44UwyT9CZPeYv/WMWxgRyf/j3Dm/tKAbpO63ZvaRO9N/6hzltPnb0dS92 mt/W4hXZhGMZR/TK6Am7PMyqKk+OFQMh5dJCfWdaQVvx34mRMJ++p0Y66mFiEhPKjZVm ZU6jiAZt5a7LMlkK8uQS5mDpsH/y6KcJD3A3g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=KULufWgLJR51+HtB9oZN9XD+CufRM+VC+UW+GVssFLM=; b=DPNfG6s9KAS0QG6V6FQjr4hNGXPUSMwyN3CFoh9czcWw3ZPfnxspWt/0qsAjuXLgws f5LMPqPm02xhWtMFo4j3EpuzsVzsyFdvJFJmDzH0MXWTGKJEKUgMEcKTTqnqgpLslV5O XFpBIdbo9k5tcWYa6Zl5kUEDSBC4KWcP7qkZISd3OaUoYo7RViQRd7lLskIpzDNNCcPs B52bp8/OgpBevimrGaSREUZo9IKnaipJ/ahd8h/8Rig64lX1gFvLE1YieMQzFv+950SB a8Vl3vSYSJsCf+MwWvu/GIiwYsGFXY/INT/P9XSsbOTZXigtsONdHbVD/UTqZMa72063 Kr7A== X-Gm-Message-State: AJcUukeX+dlUMzm4kLBAMuVMqIoz8NJcS9fHzrrjrZkUZG3KlZP0R+YZ Oh6KNtkyJxrHMiCksz0NkGbP/1lemAuycplfXjoD8w== X-Google-Smtp-Source: ALg8bN59DFUkCMMbt6Fk4T4CcTSGY4FaTQmNLpVyuEESMjcovCdS20aroTyIGG53sfIHLlp9gUcHn7Tv+o54Qsen/3c= X-Received: by 2002:ab0:7251:: with SMTP id d17mr10322749uap.0.1547492211376; Mon, 14 Jan 2019 10:56:51 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Ahrens Date: Mon, 14 Jan 2019 10:56:38 -0800 Message-ID: Subject: Re: January OpenZFS Leadership Meeting To: developer , illumos-zfs , zfs-devel@list.zfsonlinux.org, zfs-devel@freebsd.org, freebsd-fs , zfs-discuss X-Rspamd-Queue-Id: B4C6B709FE X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=delphix.com header.s=google header.b=YSohpUZd; dmarc=pass (policy=none) header.from=delphix.com; spf=pass (mx1.freebsd.org: domain of matthew.ahrens@delphix.com designates 2607:f8b0:4864:20::930 as permitted sender) smtp.mailfrom=matthew.ahrens@delphix.com X-Spamd-Result: default: False [-4.51 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RCPT_COUNT_FIVE(0.00)[6]; DKIM_TRACE(0.00)[delphix.com:+]; DMARC_POLICY_ALLOW(-0.50)[delphix.com,none]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; FORGED_SENDER(0.30)[mahrens@delphix.com,matthew.ahrens@delphix.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[mahrens@delphix.com,matthew.ahrens@delphix.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[delphix.com:s=google]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[0.3.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.83)[ipnet: 2607:f8b0::/32(-2.31), asn: 15169(-1.77), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 18:56:54 -0000 The meeting notes and recording are now available: https://www.youtube.com/watch?v=Li8Z08KZvg8 https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit?ts=5bb3b66c The next meeting will be January 29 at 11AM Pacific time. Note that this is 1 week and 2 hours earlier than the regular schedule. --matt On Mon, Jan 7, 2019 at 11:13 AM Matthew Ahrens wrote: > The next OpenZFS Leadership meeting will be held tomorrow, January 8th, > 1:00-2:00pm Pacific time, and we plan to hold this every 4 weeks > thereafter. Everyone is welcome to attend and participate, and we will try > to keep the meeting on agenda and on time. The meetings will be held > online via Zoom, and recorded and posted to the website and YouTube after > the meeting. > > The agenda for the meeting will be a discussion of the projects listed in > the agenda doc. > > For more information and details on how to attend, as well as notes and > video from the previous meeting, please see the agenda document: > > > https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit > > --matt > > From owner-freebsd-fs@freebsd.org Wed Jan 16 07:43:56 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B688114A5DE7 for ; Wed, 16 Jan 2019 07:43:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 502E390D77 for ; Wed, 16 Jan 2019 07:43:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0E76014A5DD2; Wed, 16 Jan 2019 07:43:56 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFEFF14A5DD1 for ; Wed, 16 Jan 2019 07:43:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7713090D71 for ; Wed, 16 Jan 2019 07:43:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B1388265B for ; Wed, 16 Jan 2019 07:43:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0G7hsVF059928 for ; Wed, 16 Jan 2019 07:43:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0G7hsqG059927 for fs@FreeBSD.org; Wed, 16 Jan 2019 07:43:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 234906] kernel panic: softdep_setup_inomapdep: dependency 0xfffff80107d15c00 for newinode already exists Date: Wed, 16 Jan 2019 07:43:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: johanvz816@giantfoo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 07:43:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234906 --- Comment #18 from johan van Zanten --- Thanks for the suggestions Kirk & Conrad. I'll do some experiments this weekend and see if i can come up with a way to reliably trigger the panic, and then look at disabling TRIM and then the di= sk's write cache. As for the disk cache on the hard disk, here's information about it: dejacque:~ # camcontrol identify da0 pass3: ATA8-ACS SATA 3.x device pass3: 40.000MB/s transfers protocol ATA/ATAPI-8 SATA 3.x device model HGST HTS541010A9E680 firmware revision JA0OA560 serial number JD1008DM0W2BEV WWN 5000cca827cc4ee9 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 4096, offset 0 LBA supported 268435455 sectors LBA48 supported 1953525168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6=20 media RPM 5400 Zoned-Device Commands no Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags NCQ Queue Management no NCQ Streaming no Receive & Send FPDMA Queued no SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 128/0x80 automatic acoustic management no no media status notification no no power-up in Standby yes no write-read-verify no no unload yes yes general purpose logging yes yes free-fall no no Data Set Management (DSM/TRIM) no Host Protected Area (HPA) yes no 1953525168/1953525168 HPA - Security no --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Jan 16 23:14:30 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 544E21498A8B for ; Wed, 16 Jan 2019 23:14:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E44958BC35 for ; Wed, 16 Jan 2019 23:14:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A43431498A8A; Wed, 16 Jan 2019 23:14:29 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9285F1498A89 for ; Wed, 16 Jan 2019 23:14:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DB0E8BC31 for ; Wed, 16 Jan 2019 23:14:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 68D2DB0B9 for ; Wed, 16 Jan 2019 23:14:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0GNESqI087850 for ; Wed, 16 Jan 2019 23:14:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0GNES8Z087849 for fs@FreeBSD.org; Wed, 16 Jan 2019 23:14:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 219433] ZFS volume cannot be created by delegated user Date: Wed, 16 Jan 2019 23:14:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: p5B2E9A8F@t-online.de X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 23:14:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219433 p5B2E9A8F@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 17 10:31:03 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A31D148E284; Thu, 17 Jan 2019 10:31:03 +0000 (UTC) (envelope-from SRS0=JHsv=PZ=perdition.city=julien@bebif.be) Received: from orval.bbpf.belspo.be (orval.bbpf.belspo.be [193.191.208.90]) by mx1.freebsd.org (Postfix) with ESMTP id 0C89F86944; Thu, 17 Jan 2019 10:31:01 +0000 (UTC) (envelope-from SRS0=JHsv=PZ=perdition.city=julien@bebif.be) Received: from mordor.lan (213.219.145.216.adsl.dyn.edpnet.net [213.219.145.216]) by orval.bbpf.belspo.be (Postfix) with ESMTPSA id 0B6A31D4FC18; Thu, 17 Jan 2019 11:30:54 +0100 (CET) Date: Thu, 17 Jan 2019 11:30:43 +0100 From: Julien Cigar To: freebsd-questions@freebsd.org Cc: freebsd-fs@freebsd.org Subject: Supermicro HBA Message-ID: <20190117103043.GA44618@mordor.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.11.1 (2018-12-01) X-Rspamd-Queue-Id: 0C89F86944 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of SRS0=JHsv=PZ=perdition.city=julien@bebif.be designates 193.191.208.90 as permitted sender) smtp.mailfrom=SRS0=JHsv=PZ=perdition.city=julien@bebif.be X-Spamd-Result: default: False [-3.96 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[perdition.city]; NEURAL_SPAM_SHORT(0.26)[0.256,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.21)[asn: 2611(-1.06), country: BE(0.00)]; MX_GOOD(-0.01)[mx1.bebif.be,mx2.bebif.be]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[90.208.191.193.list.dnswl.org : 127.0.10.0]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[julien@perdition.city,SRS0=JHsv=PZ=perdition.city=julien@bebif.be]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[216.145.219.213.zen.spamhaus.org : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:2611, ipnet:193.191.192.0/19, country:BE]; FROM_NEQ_ENVFROM(0.00)[julien@perdition.city,SRS0=JHsv=PZ=perdition.city=julien@bebif.be]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 10:31:03 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, We are planning to replace some (web) applications servers (currently running HPE) with Supermicro and the vendor offers the following=20 choices for the Hardware Raid Controller/HBA 4P part: 1) Supermicro AOC-S3008L-L8E, LSI 3008 8 x SATA/SAS III JBOD controller, up to 122 hard drives via expander backplane, PCI-E, ideal for Nexenta/ZFS + =E2=82=AC 205,6 2) LSI 9300-4I, SATA/SAS III JBOD controller, tot 256 harde schijven via expander backplanes, PCI-E, ideal for Nexenta/ZFS + =E2=82=AC 214,5 3) LSI MegaRAID 9341-4i bulk, 4 x SATA/SAS 12Gbs internal entry level hardware RAID, no cache/BBU possible, PCI-e + =E2=82=AC 177,97 4) LSI MegaRAID 9361-4i 1GB cache, 4 x SATA/SAS 12Gbs internal hardware RAID, max. 240 hdd using expander backplanes + =E2=82=AC 401,7 5) LSI 9300-4i4e, SATA/SAS III JBOD controller, 4 x internal, 4 x external, up to 256 hard drives via expander backplane, Nexenta Certified, ideal for ZFS, PCI-E + =E2=82=AC 273,95 6) LSI MegaRAID 9380-4i4e bulk, 8 x SATA/SAS 12Gbs, 4 x external and 4 x internal hardware RAID, 1024MB cache, up to 128 hard drives via expander backplane, support for SSD CacheCade 2.0 write and read caching, CacheVault support (advised), ideal for high en + =E2=82=AC 676 As the plan is to use ZFS, I was planning to choose the=20 "Supermicro AOC-S3008L-L8E, LSI 3008" (it looks like it is supported by mpr) and I was wondering if anyone has any feedback on it ? Would another option be a better choice ? Thank you! Julien --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7vn2l0to0nV7EWolsrs3EKIEI8AFAlxAWVAACgkQsrs3EKIE I8B2vw//VFo5enp9QXEITZUQil5rcnfoFnHm9RntxytWP5k1/PW7Ia/V2DcWAqgk rPa0Eti7BIzZ3xhUb9fBSqTjpb090/PnknF4M0ossY7T17VCFuAEcvA1SWTD64ez p2m9itE3/GsrEOlLKiJjVuqVjhzWha+CYu6ooCzJmCs8+voHbkBr7RXGUYpwY+Zu wPvSkV9g6tIB8uv4opXovN4fR9Owc2EnYH3PuHFC3iUVQMephlt0wDRui5KrtcSK ROCzyXi3R1D8xKLxLBOIf6xNqXgbZxcVtzT/u/181q8ucAyk8nfO5qdZ5DkX0/0M obk4nDpdt6SB2hFtUNGGBOGVlpEzK3Jr8d85dS/aRGS3FPMcjKS+3VheG6dOiUIu 8aSqKzsXblbSvWIFfuIBQRpRNvJkWr3XXcoxRunHdb+9Z82zZspDaosiDoztyq9L bX5hyp+0w4v6ah7SdNxQv760Qbly2JdyM1KpZxNWt7lp1DBuvAg8OHCgpiQWFfCq Vs0+ChILBFdAEtynU8F9n6EH0XKVtxiAcopHKCsuOuW173Vmx6gmbhsHPDrKYUWX QUj6RyHxhqeTyLsX/LykVZHv3OdiTl5g7Pen5H77SCmsBf6ZqjiUmia9H07G2s+T 3VW7Hb/0JuTsyKvVTjVIeoQuAjnHlNdOWQTz0hXJnggsS8OyM0Y= =8dEM -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-fs@freebsd.org Thu Jan 17 12:50:28 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 691671493C36 for ; Thu, 17 Jan 2019 12:50:28 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic301-31.consmr.mail.ne1.yahoo.com (sonic301-31.consmr.mail.ne1.yahoo.com [66.163.184.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 291FD8C2B9 for ; Thu, 17 Jan 2019 12:50:27 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: b9zrMc8VM1nwYfaU62zVK1A81oavRI..FQNj1Q1UVgzVqKF.il_NDj.dwKd6bSa 4T8ZHETboz5UZ9dh79GETJ2gNtOoVWnJ4xobwLaEEOzzDU_blfuGjUFV3Dfiex54BFDZ73q90f_C Dm5JLwNmdFyKm05d7DmDZcA3OmVJfahLve.eWTxq8Uc9EOqyr7t_VhNoqOxGcwFonpzGSv0kmKy8 B_zz2_DtshKN8Oqo2miHbpDTqSmzbMqz7SCCjgi2.MBHjzv5W8y5P6xPxdMt9IP8dVhUzBa267TN wSphWyiDrh6GVkyPsWzMCC04BfmN2Jp88c166gk7nJfjjnj3zhpauiTgntzbu_ajlBf0TQMMErmJ zPGyH6puyiUmAFCp.pJaKkGCu4KPd75L9H6ciKl3bXhazEWpjGgz.wNzOw8xSLIGA3xQ_Qzg2x7a mo_m54OD_rz7ytatuGECQWOYndOQcWErjYbTJa18qlw7C7FZJueLRcVBk.FDd5k5POdvRopCF2zK k7VV8q45RcxJEAUYbGyA3Jhm2SAYDezGMBTIYo5246pyZtlB4uFzXEW5JimNiV1197986tTNCZTD D9PzUYZw3PPW_nsZzynXRxdguCcavj3VK9pIeLbzU1RG9LtsGqFNWqtcrWNwg2uyJ2MfSioy2370 7ri4ob3AEhIhd93ICtDGeZNrB5HxNXV68Qa9rNGFuxZ8Qr05KbEttUh1IVGfp4_Y62XRKxXtBzIs GU1IaTPKXh12VbTV5ATyZvoJHCUJ_5qXecUwm35StPDE5ujVkoZWifCvC2bd7.uV_rXEsFvbxP5P rgF4uopDktE2j20.Cl1fj0VyZkMOA5rhXpppcbNGTySxlIQGbGfi0SuThXabTF.mai0vA1CFGpI3 gfmndTYKkQbTdkGXlnv3cu82aQ0MRavJHkd89iYIP.fMwYp8im.b82ha0_.vj1fvVukpXpXx0TDL CpUhyYIdNdr0F0Fxz41q3MncHxPkNLUiUwXE_IWasvZWKCg7ssfCS2t9Bcsk2BhHSI_DzJQM3N07 8k3z649yJLb1tEOvFKAQsCStDN.SoczO3fh63MmYholuQor2HT3q93KhBuPssvmCyXpp0Nl9GCEE n8IYc_BfoAA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.ne1.yahoo.com with HTTP; Thu, 17 Jan 2019 12:50:26 +0000 Date: Thu, 17 Jan 2019 12:50:22 +0000 (UTC) From: Paul Pathiakis To: freebsd-questions@freebsd.org, Julien Cigar Cc: freebsd-fs@freebsd.org Message-ID: <1443717602.966565.1547729422870@mail.yahoo.com> In-Reply-To: <20190117103043.GA44618@mordor.lan> References: <20190117103043.GA44618@mordor.lan> Subject: Re: Supermicro HBA MIME-Version: 1.0 X-Mailer: WebService/1.1.12857 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 X-Rspamd-Queue-Id: 291FD8C2B9 X-Spamd-Bar: +++ X-Spamd-Result: default: False [3.17 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.79)[0.786,0]; MANY_INVISIBLE_PARTS(0.40)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.97)[0.968,0]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; RCVD_IN_DNSWL_NONE(0.00)[200.184.163.66.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; IP_SCORE(1.06)[ip: (3.43), ipnet: 66.163.184.0/21(1.09), asn: 36646(0.88), country: US(-0.08)]; NEURAL_SPAM_LONG(0.96)[0.964,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36646, ipnet:66.163.184.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 12:50:28 -0000 I've used the LSI 3008.=C2=A0 I haven't had any issues with it.=C2=A0 It i= s supported by that driver.=C2=A0 (I haven't built a server with one lately= ) Yes, avoid all the hardware RAID cards they are unnecessary and a JBOD cont= roller with ZFS is a good choice.=C2=A0 Make sure it supports the SAS3 spec= of 12 Gb/s.=C2=A0 That's where the speed is.=C2=A0 I found the following a= s an FYI. Supermicro LSI SAS3008 HBA Review | StorageReview.com - Storage Reviews |=20 |=20 |=20 | | | | | |=20 | |=20 Supermicro LSI SAS3008 HBA Review | StorageReview.com - Storage Reviews The Supermicro LSI SAS3008 HBAs (which share the same controller as the LSI= 9300-8i HBAs) are engineered to deli... | | | I looked at it as more of a specs education.=C2=A0 It looks solid.=C2=A0 I'= ve used Supermicro without issue in the past.=C2=A0 (I just decommissioned = my home server which was Supermicro and has that very card in it.) There is a lot to consider when using ZFS beyond just the hardware.=C2=A0 D= on't get me wrong.... I want to have ZFS' baby.=C2=A0 :D=C2=A0 Just be sure= of all the nuances of HDD, SSD, Hybrids, how much memory you have to dedic= ate to ZFS and CPU cores you have.=C2=A0 You have to take into consideratio= n all the ZFS features you're planning to make use of now and in the future= . Also, are you ever planning on expanding the storage to have an additional = JBOD shelf?=C2=A0 If so, you may want a card with some external connectors.= =C2=A0=C2=A0 Some of the people at=C2=A0http://www.ixsystems.com=C2=A0have done some ser= ious research on application specific throughput of ZFS and I believe they = also spec out SuperMicro servers too.=C2=A0 It comes down to IOPS, raw thro= ughput, etc.=C2=A0 (I'm actually talking to them right now about some very = large backup servers that can handle 0.75 PB.... The consideration I have i= s space and using RAIDZ2 and multiple streams from 10Gb interfaces and seri= ous compression and deduplication.=C2=A0 SO,=C2=A0 IOPS not so much, but he= avy raw I/O and RAID checksum computation and dedup. There's also things like dedicated SSDs as ZIL and cache to be thought abou= t. So:=C2=A0 go up the theoretical OSI layer model and optimize each layer rig= ht through the application layer. :D=C2=A0 (I actually find it fun) I hope this all helps. P On Thursday, January 17, 2019, 4:33:38 AM CST, Julien Cigar wrote: =20 =20 Hello, We are planning to replace some (web) applications servers (currently running HPE) with Supermicro and the vendor offers the following=20 choices for the Hardware Raid Controller/HBA 4P part: 1) Supermicro AOC-S3008L-L8E, LSI 3008 8 x SATA/SAS III JBOD controller, up to 122 hard drives via expander backplane, PCI-E, ideal for Nexenta/ZFS + =E2=82=AC 205,6 2) LSI 9300-4I, SATA/SAS III JBOD controller, tot 256 harde schijven via expander backplanes, PCI-E, ideal for Nexenta/ZFS + =E2=82=AC 214,5 3) LSI MegaRAID 9341-4i bulk, 4 x SATA/SAS 12Gbs internal entry level hardware RAID, no cache/BBU possible, PCI-e + =E2=82=AC 177,97 4) LSI MegaRAID 9361-4i 1GB cache, 4 x SATA/SAS 12Gbs internal hardware RAID, max. 240 hdd using expander backplanes + =E2=82=AC 401,7 5) LSI 9300-4i4e, SATA/SAS III JBOD controller, 4 x internal, 4 x external, up to 256 hard drives via expander backplane, Nexenta Certified, ideal for ZFS, PCI-E + =E2=82=AC 273,95 6) LSI MegaRAID 9380-4i4e bulk, 8 x SATA/SAS 12Gbs, 4 x external and 4 x internal hardware RAID, 1024MB cache, up to 128 hard drives via expander backplane, support for SSD CacheCade 2.0 write and read caching, CacheVault support (advised), ideal for high en + =E2=82=AC 676 As the plan is to use ZFS, I was planning to choose the=20 "Supermicro AOC-S3008L-L8E, LSI 3008" (it looks like it is supported by mpr) and I was wondering if anyone has any feedback on it ? Would another option be a better choice ? Thank you! Julien --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11=C2=A0 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. =20 From owner-freebsd-fs@freebsd.org Thu Jan 17 14:28:35 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35EDB149840C; Thu, 17 Jan 2019 14:28:35 +0000 (UTC) (envelope-from tenzin.lhakhang@gmail.com) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBC8B69F85; Thu, 17 Jan 2019 14:28:33 +0000 (UTC) (envelope-from tenzin.lhakhang@gmail.com) Received: by mail-lf1-x12a.google.com with SMTP id p6so7979937lfc.1; Thu, 17 Jan 2019 06:28:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xcSamRnxJ5mCx4pHfNQf3p/f43LG3kj8W7WvVqf5kZg=; b=BiJOv4EpScLBe8vG6Nwgagb1cz1jo6/HmPE4vuwHcnUxSDzO0qZ5TFEh3kpGZl0EJ8 MS98WkgAPCdZoNb5HEmvav9kLf956QawHHJdUIprnvQvRGAPscrGesWxBZw9yUj4NxVX 1EJWYwXQUpQSLPOAtyh/02gk4pzcR2q9cuSQhofSBtPMZ6YOLPOQr1a8UduJVjhqYLce 5QtHbcxnfVd4mAHRMLLSoBuNtPfW6GrZHwZ7nl3DNPJv4hXxaXJxlNn4yQSfzCnpfqFF cIEThodTzqy6WxS8x4v9B5ZQiOtoCO/J7bM1SbEBTBunjERI4gG4admoUM7iBheZpQFV K1wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xcSamRnxJ5mCx4pHfNQf3p/f43LG3kj8W7WvVqf5kZg=; b=a74E22u5F6ZPdGcOK5lr/AXLQ7CQDQATJzttBzz8WeyU0Q3GZinawSdAJlEcmofuef BuBZte1oNJF0r+prAfM/5AUXRdXQ2dyTUJHuT1HiBY55N7RT6fpLfB4qyXy/vIPITOhO VXkFwEJETheJjuwvn4lszDfaDFDOZs0nqrbmVJlofJRPqvEXJg4tpiVCkmWt5c3/LGvi TzJcAbdRudP3ICwJfIlDtnkQ37IlAyqJhgKCgJ1S65wIfZW42dMbVMlayNitpce/gf6Q Fohj3Wpo70XoD0+CpF6X8iZ96UToDiBhVPd01xlhb6zlSSYnXEAn3oDE/KAx5xIAQwK1 s9xQ== X-Gm-Message-State: AJcUukdp+9sp1tqwlQKAtW+9DDGHgvacGt/p5SCQBO9cJyZm6KURkfGU IOsw8yCV3EaiNw6vl8QNuOkVqtsgp7Ebd7bCfzXh7+Zs X-Google-Smtp-Source: ALg8bN6pRyhnvI1HrPuBlkqJttA2tfWQG9kCqXhrqYbA/aNSqROTAitaQXvnJN74ogQClC2XZ90EYEXvJTreOzMw8sE= X-Received: by 2002:a19:518d:: with SMTP id g13mr10123601lfl.143.1547735312156; Thu, 17 Jan 2019 06:28:32 -0800 (PST) MIME-Version: 1.0 References: <20190117103043.GA44618@mordor.lan> <1443717602.966565.1547729422870@mail.yahoo.com> In-Reply-To: <1443717602.966565.1547729422870@mail.yahoo.com> From: Tenzin Lhakhang Date: Thu, 17 Jan 2019 09:28:20 -0500 Message-ID: Subject: Re: Supermicro HBA To: Paul Pathiakis Cc: freebsd-questions@freebsd.org, Julien Cigar , "freebsd-fs@FreeBSD.org" X-Rspamd-Queue-Id: DBC8B69F85 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=BiJOv4Ep; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of tenzinlhakhang@gmail.com designates 2a00:1450:4864:20::12a as permitted sender) smtp.mailfrom=tenzinlhakhang@gmail.com X-Spamd-Result: default: False [-6.55 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.93)[-0.925,0]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.61)[ip: (-9.11), ipnet: 2a00:1450::/32(-2.07), asn: 15169(-1.81), country: US(-0.08)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 14:28:35 -0000 If cost is negligible between Supermicro HBA using 3008 controller versus Broadcom/Avago/LSI card. I'd say opt for the Broadcom card, their support + drivers + firmware downloads is much better than Supermicro's FTP site. Broadcom keeps whitepapers, archive of all their past released firmwares. Must dos: - Make sure to do hot-add hot-remove disks (with workload). - Make sure to do disk led blink light tests. You will have to use the sas3ircu utility, unless you have OS specific utilities to find them. - Perform an fio disk benchmark to get baseline system performance. https://github.com/axboe/fio Issues I've seen: - SuperMicro's FTP site for their firmware doesn't include archive copies, only latest. Sometimes latest FW doesn't work nicely and hopefully you have an old FW downloaded prior. - SuperMicro FTP site: ftp://ftp.supermicro.com/Driver/SAS/LSI/ - Sometimes SM HBA's FW and LSI HBA's FW can be used interchangeable and sometimes not. If you flashed a LSI HBA with SMC firmware, then you have to add -nossid when flashing using the sas3flash when going back to LSI firmware. Sometimes it flashes fine and everything looks ok, you see all the disks, but when you blink disk 4, it blinks disk 1. When you physically remove disk 2, ZFS says disk 3 is gone. It's best to thoroughly qualify the system after FW flash. Broadcom page for 9300-8i - https://www.broadcom.com/products/storage/host-bus-adapters/sas-9300-8i#ove= rview - It's a bit hard to understand all the different downloads, but they're helpful when you understand the workflow to flash FW and use the sas3ircu utility. In the latest release, they've bundled all the required downloads into the Firmware download. In the past you would have to individually find the different ROM and BIN files. All said, Supermicro HBA when it's working, it works pretty well. I've seen HBA failures, but the systems were usually 5+ years old. - If you have multiple HBAs in a system, record which physical controller is on PCIe slot is the logical controller reported by OS. Otherwise when a single HBA fails, it's a bit hard to trace which software HBA is which physical HBA. Thanks, Tenzin On Thu, Jan 17, 2019 at 7:51 AM Paul Pathiakis via freebsd-fs < freebsd-fs@freebsd.org> wrote: > I've used the LSI 3008. I haven't had any issues with it. It is > supported by that driver. (I haven't built a server with one lately) > Yes, avoid all the hardware RAID cards they are unnecessary and a JBOD > controller with ZFS is a good choice. Make sure it supports the SAS3 spe= c > of 12 Gb/s. That's where the speed is. I found the following as an FYI. > Supermicro LSI SAS3008 HBA Review | StorageReview.com - Storage Reviews > > > | > | > | > | | | > > | > > | > | > | | > Supermicro LSI SAS3008 HBA Review | StorageReview.com - Storage Reviews > > The Supermicro LSI SAS3008 HBAs (which share the same controller as the > LSI 9300-8i HBAs) are engineered to deli... > | > > | > > | > > > I looked at it as more of a specs education. It looks solid. I've used > Supermicro without issue in the past. (I just decommissioned my home > server which was Supermicro and has that very card in it.) > There is a lot to consider when using ZFS beyond just the hardware. Don'= t > get me wrong.... I want to have ZFS' baby. :D Just be sure of all the > nuances of HDD, SSD, Hybrids, how much memory you have to dedicate to ZFS > and CPU cores you have. You have to take into consideration all the ZFS > features you're planning to make use of now and in the future. > Also, are you ever planning on expanding the storage to have an additiona= l > JBOD shelf? If so, you may want a card with some external connectors. > Some of the people at http://www.ixsystems.com have done some serious > research on application specific throughput of ZFS and I believe they als= o > spec out SuperMicro servers too. It comes down to IOPS, raw throughput, > etc. (I'm actually talking to them right now about some very large backu= p > servers that can handle 0.75 PB.... The consideration I have is space and > using RAIDZ2 and multiple streams from 10Gb interfaces and serious > compression and deduplication. SO, IOPS not so much, but heavy raw I/O > and RAID checksum computation and dedup. > There's also things like dedicated SSDs as ZIL and cache to be thought > about. > So: go up the theoretical OSI layer model and optimize each layer right > through the application layer. :D (I actually find it fun) > I hope this all helps. > P > > On Thursday, January 17, 2019, 4:33:38 AM CST, Julien Cigar > wrote: > > Hello, > > We are planning to replace some (web) applications servers (currently > running HPE) with Supermicro and the vendor offers the following > choices for the Hardware Raid Controller/HBA 4P part: > > 1) Supermicro AOC-S3008L-L8E, LSI 3008 8 x SATA/SAS III JBOD controller, = up > to 122 hard drives via expander backplane, PCI-E, ideal for Nexenta/ZFS > + =E2=82=AC 205,6 > > 2) LSI 9300-4I, SATA/SAS III JBOD controller, tot 256 harde schijven via > expander backplanes, PCI-E, ideal for Nexenta/ZFS > + =E2=82=AC 214,5 > > 3) LSI MegaRAID 9341-4i bulk, 4 x SATA/SAS 12Gbs internal entry level > hardware RAID, no cache/BBU possible, PCI-e > + =E2=82=AC 177,97 > > 4) LSI MegaRAID 9361-4i 1GB cache, 4 x SATA/SAS 12Gbs internal > hardware RAID, max. 240 hdd using expander backplanes > + =E2=82=AC 401,7 > > 5) LSI 9300-4i4e, SATA/SAS III JBOD controller, 4 x internal, 4 x externa= l, > up to 256 hard drives via expander backplane, Nexenta Certified, ideal > for ZFS, PCI-E > + =E2=82=AC 273,95 > > 6) LSI MegaRAID 9380-4i4e bulk, 8 x SATA/SAS 12Gbs, 4 x external and 4 x > internal hardware RAID, 1024MB cache, up to 128 hard drives via expander > backplane, support for SSD CacheCade 2.0 write and read caching, > CacheVault support (advised), ideal for high en > + =E2=82=AC 676 > > As the plan is to use ZFS, I was planning to choose the > "Supermicro AOC-S3008L-L8E, LSI 3008" (it looks like it is supported by > mpr) and I was wondering if anyone has any feedback on it ? Would > another option be a better choice ? > > Thank you! > Julien > > -- > Julien Cigar > Belgian Biodiversity Platform (http://www.biodiversity.be) > PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 > No trees were killed in the creation of this message. > However, many electrons were terribly inconvenienced. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Thu Jan 17 23:35:03 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0389E1484081 for ; Thu, 17 Jan 2019 23:35:03 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95C268B236 for ; Thu, 17 Jan 2019 23:35:00 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: by mail-lj1-x22f.google.com with SMTP id u89-v6so10103612lje.1 for ; Thu, 17 Jan 2019 15:35:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=5gPTchVAZ6G7LKRphqzzPRJng5SLfP+3zK3GG0QfVfY=; b=bL7R623ky3LrdjkBqzeqi5GCJAtvoeyCe7wlPN9vnNCmzldkuqhzLvcK0rUVnL3bBo nyM647R5mwXNSja/AskkT+9hyLZh4OiFL1VzjM85JTerQmAz8dzdG8+zmfTNbcOp0KkU 8intYpKa16xdL9rkewdDT4jogqaeZF7h+TvJE0dlWeadq2RkHCBocqmuN3HZml3+wKt6 lR58c7GJXHMeCB/zfFN+y2rmKEafEQj2YD8quSX4Crftf+88KrdXQkqTQ6NJLnkmcVlt KhMCAalS/zmJs3NDcpFsJM8HcuXEVbaiYPsDXsyFdOoCfl1qgKzDJPy4AQQQRye6a3C1 JytA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5gPTchVAZ6G7LKRphqzzPRJng5SLfP+3zK3GG0QfVfY=; b=LC637j1LsKXXCVQudUHk3+doqEo5toJmssgcUgka9RPQBoW3UPj542O7CuooDgnqb7 XNgQ9TR6lBaUSnydj3iLC/wLbl/Qj71eKHU39IzzMWfXgzmHzETPS8mSL/AMDVef4HD3 UlBl7YpmzGJuH9KSYUA16rvbGTO+Fx4AjKaJ5SMENWVhrMtwFmtWUA6TGqaXkTv7i6mW nOMXuFtqsSIX1WIU1QGphkezs4oO3Bhw/k8tMKbuAqgLAnvMOagbcLaGcZubmVBJXgnU C9zETxIG5bMIl6NV29BoJCsKVA+QXNMuvqmy8miHtxgV4bLtHlpmCeysiA3HnQSopTyf FPHg== X-Gm-Message-State: AJcUukcGQqalqz0bAmDaTFEB4EYASb6YAllYnxIPaanjZk0cz+sqbEPf ez7Y5A3IcSLI41fRFiFEzpKCbmDyUtG0YR+QqcjAOFFQ X-Google-Smtp-Source: ALg8bN7IxyApnY8Tr+9wH+d4KiOB3rD+R0AN6oiewlSC33kNJF20s//mLAbbVsn9v985oSsi33XrI4lurHErD+RlKHA= X-Received: by 2002:a2e:2a06:: with SMTP id q6-v6mr10373550ljq.37.1547768097507; Thu, 17 Jan 2019 15:34:57 -0800 (PST) MIME-Version: 1.0 From: jdelisle Date: Thu, 17 Jan 2019 17:34:46 -0600 Message-ID: Subject: "zpool remove" failing To: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 95C268B236 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=bL7R623k; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdelisle@gmail.com designates 2a00:1450:4864:20::22f as permitted sender) smtp.mailfrom=jdelisle@gmail.com X-Spamd-Result: default: False [-6.47 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.87)[-0.866,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.69)[ip: (-9.47), ipnet: 2a00:1450::/32(-2.08), asn: 15169(-1.82), country: US(-0.08)]; RCVD_IN_DNSWL_NONE(0.00)[f.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 23:35:03 -0000 Hello, I've run into a problem and I'm hoping the knowledgeable folks here can help. I've accidentally added a mirror vdev to a pool, and would like to remove it. Note "mirror-8" in the output down below, it's what I'd like to remove. When I attempt to remove it, I get the following message: [root@omega ~]# zpool remove nebula mirror-8 cannot remove mirror-8: invalid config; all top-level vdevs must have the same sector size and not be raidz. The disks in my pool are all 512 byte sector disks. Any idea what I'm doing wrong? ##### My system's uname -a - it's FreeNAS. [root@omega ~]# uname -a FreeBSD omega.nebula.pw 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+fc3d65faae6(HEAD): Thu Dec 20 16:12:30 EST 2018 root@nemesis.tn.ixsystems.com:/freenas-releng-final/freenas/_BE/objs/freenas-releng-final/freenas/_BE/os/sys/FreeNAS.amd64 amd64 ##### The pool I accidentally added a mirror vdev to (mirror-8): [root@omega ~]# zpool status -v nebula pool: nebula state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM nebula ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/2fdc125f-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/30816c63-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gptid/31403c46-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/31f1f182-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gptid/32a4cfa3-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/3356fcab-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 gptid/341311e6-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/34c9952c-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-4 ONLINE 0 0 0 gptid/3580b3ad-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/364188ba-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-5 ONLINE 0 0 0 gptid/370908e5-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/37cf00a5-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-6 ONLINE 0 0 0 gptid/388e6fef-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/3945fee7-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-7 ONLINE 0 0 0 gptid/3a08fb45-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 gptid/3ad7a643-15f4-11e9-b1b0-000c29f308bf ONLINE 0 0 0 mirror-8 ONLINE 0 0 0 da33p1 ONLINE 0 0 0 da34p1 ONLINE 0 0 0 errors: No known data errors [root@omega ~]# ##### My ZFS features etc. [root@omega ~]# zpool get all nebula NAME PROPERTY VALUE SOURCE nebula size 21.8T - nebula capacity 64% - nebula altroot /mnt local nebula health ONLINE - nebula guid 9027025247116299332 default nebula version - default nebula bootfs - default nebula delegation on default nebula autoreplace off default nebula cachefile /data/zfs/zpool.cache local nebula failmode continue local nebula listsnapshots off default nebula autoexpand on local nebula dedupditto 0 default nebula dedupratio 1.00x - nebula free 7.76T - nebula allocated 14.0T - nebula readonly off - nebula comment - default nebula expandsize - - nebula freeing 0 default nebula fragmentation 2% - nebula leaked 0 default nebula bootsize - default nebula checkpoint - - nebula feature@async_destroy enabled local nebula feature@empty_bpobj active local nebula feature@lz4_compress active local nebula feature@multi_vdev_crash_dump enabled local nebula feature@spacemap_histogram active local nebula feature@enabled_txg active local nebula feature@hole_birth active local nebula feature@extensible_dataset enabled local nebula feature@embedded_data active local nebula feature@bookmarks enabled local nebula feature@filesystem_limits enabled local nebula feature@large_blocks enabled local nebula feature@sha512 enabled local nebula feature@skein enabled local nebula feature@device_removal enabled local nebula feature@obsolete_counts enabled local nebula feature@zpool_checkpoint enabled local ###### The two disks in the mirrored vdev I wish to remove: [root@omega ~]# diskinfo -v /dev/da33 /dev/da33 512 # sectorsize 120034123776 # mediasize in bytes (112G) 234441648 # mediasize in sectors 4096 # stripesize 0 # stripeoffset 14593 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. ATA INTEL SSDSA2CW12 # Disk descr. CVPR1132000R120LGN # Disk ident. id1,enc@n50050cc1020371ce/type@0/slot@13 # Physical path Yes # TRIM/UNMAP support 0 # Rotation rate in RPM Not_Zoned # Zone Mode [root@omega ~]# diskinfo -v /dev/da34 /dev/da34 512 # sectorsize 120034123776 # mediasize in bytes (112G) 234441648 # mediasize in sectors 4096 # stripesize 0 # stripeoffset 14593 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. ATA INTEL SSDSA2CW12 # Disk descr. CVPR119300D5120LGN # Disk ident. id1,enc@n50050cc1020371ce/type@0/slot@7 # Physical path Yes # TRIM/UNMAP support 0 # Rotation rate in RPM Not_Zoned # Zone Mode [root@omega ~]# ##### This is an example of one of the many disks in my mirrored pairs. They're all the same make/ model of disk, and are 512 byte sectors just like the SSDs above. [root@omega ~]# diskinfo -v /dev/da10 /dev/da10 512 # sectorsize 3000592982016 # mediasize in bytes (2.7T) 5860533168 # mediasize in sectors 0 # stripesize 0 # stripeoffset 364801 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. HITACHI HUS72303CLAR3000 # Disk descr. YHJEXGHD # Disk ident. id1,enc@n50050cc1020371ce/type@0/slot@f # Physical path No # TRIM/UNMAP support 7200 # Rotation rate in RPM Not_Zoned # Zone Mode [root@omega ~]# From owner-freebsd-fs@freebsd.org Fri Jan 18 23:06:07 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CA3514869E4 for ; Fri, 18 Jan 2019 23:06:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 376F0810E6 for ; Fri, 18 Jan 2019 23:06:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EBF9714869E3; Fri, 18 Jan 2019 23:06:06 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8F3C14869E2 for ; Fri, 18 Jan 2019 23:06:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70785810E3 for ; Fri, 18 Jan 2019 23:06:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B80275872 for ; Fri, 18 Jan 2019 23:06:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0IN65Zc017535 for ; Fri, 18 Jan 2019 23:06:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0IN65SX017534 for fs@FreeBSD.org; Fri, 18 Jan 2019 23:06:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 140068] [smbfs] [patch] smbfs does not allow semicolon in filenames, but should Date: Fri, 18 Jan 2019 23:06:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: easy, needs-qa, patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gonzo@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: gonzo@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: bug_status cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2019 23:06:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D140068 Oleksandr Tymoshenko changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress CC| |gonzo@FreeBSD.org Assignee|fs@FreeBSD.org |gonzo@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Jan 19 15:07:24 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21A0D1482314 for ; Sat, 19 Jan 2019 15:07:24 +0000 (UTC) (envelope-from gausus@gausus.net) Received: from poczta.dzikakuna.net (poczta.dzikakuna.net [91.192.224.135]) by mx1.freebsd.org (Postfix) with ESMTP id 3B135854A5 for ; Sat, 19 Jan 2019 15:07:23 +0000 (UTC) (envelope-from gausus@gausus.net) Received: from localhost (localhost [127.0.0.1]) by poczta.dzikakuna.net (Postfix) with ESMTP id BB2B743A0A9 for ; Sat, 19 Jan 2019 16:07:14 +0100 (CET) Received: from poczta.dzikakuna.net ([127.0.0.1]) by localhost (poczta.dzikakuna.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id aS7UgbLF3RjQ for ; Sat, 19 Jan 2019 16:07:14 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by poczta.dzikakuna.net (Postfix) with ESMTP id 650CD43A0AA for ; Sat, 19 Jan 2019 16:07:14 +0100 (CET) X-Virus-Scanned: amavisd-new at metroplex.pl Received: from poczta.dzikakuna.net ([127.0.0.1]) by localhost (poczta.dzikakuna.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id UCGhuCTPiPez for ; Sat, 19 Jan 2019 16:07:14 +0100 (CET) Received: from poczta.dzikakuna.net (poczta.dzikakuna.net [91.192.224.135]) by poczta.dzikakuna.net (Postfix) with ESMTP id 48AD343A0A9 for ; Sat, 19 Jan 2019 16:07:14 +0100 (CET) Date: Sat, 19 Jan 2019 16:07:13 +0100 (CET) From: Maciej Jan Broniarz To: freebsd-fs@freebsd.org Message-ID: <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> Subject: ZFS on Hardware RAID MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC71 (Mac)/8.0.9_GA_6191) Thread-Topic: ZFS on Hardware RAID Thread-Index: RPQmwoXiTH0jd5sZ6uWLD4/zieEw4A== X-Rspamd-Queue-Id: 3B135854A5 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.74 / 15.00]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.63)[0.628,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.43)[0.427,0]; DMARC_NA(0.00)[gausus.net]; MX_GOOD(-0.01)[poczta.dzikakuna.net]; NEURAL_SPAM_LONG(0.69)[0.689,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42576, ipnet:91.192.224.0/24, country:PL]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.01)[country: PL(0.03)] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 15:07:24 -0000 Hi, I want to use ZFS on a hardware-raid array. I have no option of making it JBOD. I know it is best to use ZFS on JBOD, but that possible in that particular case. My question is - how bad of an idea is it. I have read very different opinions on that subject, but none of them seems conclusive. Any comments and especially case studies are most welcome. All best, mjb From owner-freebsd-fs@freebsd.org Sat Jan 19 16:39:19 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44FC8148680F for ; Sat, 19 Jan 2019 16:39:19 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E494089354 for ; Sat, 19 Jan 2019 16:39:17 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: by mail-lj1-x231.google.com with SMTP id u89-v6so14187301lje.1 for ; Sat, 19 Jan 2019 08:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ISU27wElB4tse8UH30BEhdWvBGgnyGWUYmOB9WPJWW8=; b=UZ42u1l1kxQhRb9vjCjVZkUCt/mPpiMJmt1oZZkSEHSSwkcsGu5iZ3WkAnMxmqNtbq xlcO/EYdutzLWR3v7AAHt/aWRUUu/hTvxlMYSZj4yfi2yJkj/tMZLuWUA8OWSp/yxhc7 5JF/M0WDW/saQGcic65OWc8+gGWuB4msOBiucAgzk4ZVCz6kJ/MB2zqGyCAW44+BqvFd rqXFK9ZGRpwqOGEOXgsnsQkkB2fKJng1jW2JuJV5VSaUVnsPD7kfMOYYNfjU0zG3K1m3 I8xgr5VLPW/P2qAFo4IaVXISXaARPhgQH1Gth3L7sZAeA3DD2+ChKdvV+Q7jO5C3a8wz CxQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ISU27wElB4tse8UH30BEhdWvBGgnyGWUYmOB9WPJWW8=; b=MiDnBh6a0T/nIK29Ek1zqaIV2WNN/JVgboKVIYftGszOQBwODv+LH4Y9RLilm665SU RAE5KbLlegC0FTlGd/aDY2p8/NbjwjgweUylN70pbrnonY4VB5ffOMBINygNh5NSr+O+ tPkKSwZGAS706h8jEAyxnWH3HToWkdAexdFWx5GFrIrboize5XCroizBqfQuGmlLkNZU pnnhbkPLokTCeAZ2vbHg3gFkgWjZh1VcVcf+yRwtCmNkwU03x2uKJThicyELaYSPomXg BBGWY/AOXyHhJXxIogt2BCplr2S0qi21BMvbFEwTo4R0cSb/CDZvwviHMEk/291MoqIa T4VA== X-Gm-Message-State: AJcUukffgcaFWJk/gQTKA6Do0xIJUojKp/QqI0WUpu9LBwYg9ZenrcEY 9oMYcP48eA5LAPKOhM2uW4to5A8SlcSIQL7t8QUMrA== X-Google-Smtp-Source: ALg8bN4oLRQ9ZNFus+KNWAf0JjC4OYrOffxcKk2O3wrrRso3YLKfFAEEM5p4DuKSL1m09WlL5CMx9PAqIFu7RksYNYo= X-Received: by 2002:a2e:1b47:: with SMTP id b68-v6mr12711871ljb.104.1547915955112; Sat, 19 Jan 2019 08:39:15 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: jdelisle Date: Sat, 19 Jan 2019 10:39:03 -0600 Message-ID: Subject: Re: "zpool remove" failing To: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: E494089354 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=UZ42u1l1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdelisle@gmail.com designates 2a00:1450:4864:20::231 as permitted sender) smtp.mailfrom=jdelisle@gmail.com X-Spamd-Result: default: False [-6.49 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.62)[ip: (-9.08), ipnet: 2a00:1450::/32(-2.11), asn: 15169(-1.83), country: US(-0.08)]; RCVD_IN_DNSWL_NONE(0.00)[1.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 16:39:19 -0000 I'm grasping at straws here, but could this functionality be incomplete in 11.2-RELEASE? Would connecting my disks to a 12.0-RELEASE system help? It's easy for me to do that, but is it safe to move them to a 12.0-RELEASE system, run the "zpool remove", then move them back to my 11.2-RELEASE system? Is there any diagnostic output I could share that would help? I'm still confused by the error I'm getting from "zpool remove".. I'm attempting to remove a top-level mirror vdev, and they're all the same sector-size. On Thu, Jan 17, 2019 at 5:34 PM jdelisle wrote: > Hello, > > I've run into a problem and I'm hoping the knowledgeable folks here can > help. > > I've accidentally added a mirror vdev to a pool, and would like to remove > it. Note "mirror-8" in the output down below, it's what I'd like to remove. > > When I attempt to remove it, I get the following message: > > [root@omega ~]# zpool remove nebula mirror-8 > cannot remove mirror-8: invalid config; all top-level vdevs must have the > same sector size and not be raidz. > > The disks in my pool are all 512 byte sector disks. > > Any idea what I'm doing wrong? > > ##### My system's uname -a - it's FreeNAS. > [root@omega ~]# uname -a > FreeBSD omega.nebula.pw 11.2-STABLE FreeBSD 11.2-STABLE #0 > r325575+fc3d65faae6(HEAD): Thu Dec 20 16:12:30 EST 2018 > root@nemesis.tn.ixsystems.com:/freenas-releng-final/freenas/_BE/objs/freenas-releng-final/freenas/_BE/os/sys/FreeNAS.amd64 > amd64 > > ##### The pool I accidentally added a mirror vdev to (mirror-8): > [root@omega ~]# zpool status -v nebula > pool: nebula > state: ONLINE > scan: none requested > config: > > NAME STATE READ > WRITE CKSUM > nebula ONLINE 0 > 0 0 > mirror-0 ONLINE 0 > 0 0 > gptid/2fdc125f-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/30816c63-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-1 ONLINE 0 > 0 0 > gptid/31403c46-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/31f1f182-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-2 ONLINE 0 > 0 0 > gptid/32a4cfa3-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/3356fcab-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-3 ONLINE 0 > 0 0 > gptid/341311e6-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/34c9952c-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-4 ONLINE 0 > 0 0 > gptid/3580b3ad-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/364188ba-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-5 ONLINE 0 > 0 0 > gptid/370908e5-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/37cf00a5-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-6 ONLINE 0 > 0 0 > gptid/388e6fef-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/3945fee7-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-7 ONLINE 0 > 0 0 > gptid/3a08fb45-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > gptid/3ad7a643-15f4-11e9-b1b0-000c29f308bf ONLINE 0 > 0 0 > mirror-8 ONLINE 0 > 0 0 > da33p1 ONLINE 0 > 0 0 > da34p1 ONLINE 0 > 0 0 > > errors: No known data errors > [root@omega ~]# > > > ##### My ZFS features etc. > [root@omega ~]# zpool get all nebula > NAME PROPERTY VALUE > SOURCE > nebula size 21.8T - > nebula capacity 64% - > nebula altroot /mnt local > nebula health ONLINE - > nebula guid 9027025247116299332 > default > nebula version - > default > nebula bootfs - > default > nebula delegation on > default > nebula autoreplace off > default > nebula cachefile /data/zfs/zpool.cache local > nebula failmode continue local > nebula listsnapshots off > default > nebula autoexpand on local > nebula dedupditto 0 > default > nebula dedupratio 1.00x - > nebula free 7.76T - > nebula allocated 14.0T - > nebula readonly off - > nebula comment - > default > nebula expandsize - - > nebula freeing 0 > default > nebula fragmentation 2% - > nebula leaked 0 > default > nebula bootsize - > default > nebula checkpoint - - > nebula feature@async_destroy enabled > local > nebula feature@empty_bpobj active > local > nebula feature@lz4_compress active > local > nebula feature@multi_vdev_crash_dump enabled > local > nebula feature@spacemap_histogram active > local > nebula feature@enabled_txg active > local > nebula feature@hole_birth active > local > nebula feature@extensible_dataset enabled > local > nebula feature@embedded_data active > local > nebula feature@bookmarks enabled > local > nebula feature@filesystem_limits enabled > local > nebula feature@large_blocks enabled > local > nebula feature@sha512 enabled > local > nebula feature@skein enabled > local > nebula feature@device_removal enabled > local > nebula feature@obsolete_counts enabled > local > nebula feature@zpool_checkpoint enabled > local > > ###### The two disks in the mirrored vdev I wish to remove: > [root@omega ~]# diskinfo -v /dev/da33 > /dev/da33 > 512 # sectorsize > 120034123776 # mediasize in bytes (112G) > 234441648 # mediasize in sectors > 4096 # stripesize > 0 # stripeoffset > 14593 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > ATA INTEL SSDSA2CW12 # Disk descr. > CVPR1132000R120LGN # Disk ident. > id1,enc@n50050cc1020371ce/type@0/slot@13 # Physical path > Yes # TRIM/UNMAP support > 0 # Rotation rate in RPM > Not_Zoned # Zone Mode > > [root@omega ~]# diskinfo -v /dev/da34 > /dev/da34 > 512 # sectorsize > 120034123776 # mediasize in bytes (112G) > 234441648 # mediasize in sectors > 4096 # stripesize > 0 # stripeoffset > 14593 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > ATA INTEL SSDSA2CW12 # Disk descr. > CVPR119300D5120LGN # Disk ident. > id1,enc@n50050cc1020371ce/type@0/slot@7 # Physical path > Yes # TRIM/UNMAP support > 0 # Rotation rate in RPM > Not_Zoned # Zone Mode > > [root@omega ~]# > > > ##### This is an example of one of the many disks in my mirrored pairs. > They're all the same make/ model of disk, and are 512 byte sectors just > like the SSDs above. > [root@omega ~]# diskinfo -v /dev/da10 > /dev/da10 > 512 # sectorsize > 3000592982016 # mediasize in bytes (2.7T) > 5860533168 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 364801 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > HITACHI HUS72303CLAR3000 # Disk descr. > YHJEXGHD # Disk ident. > id1,enc@n50050cc1020371ce/type@0/slot@f # Physical path > No # TRIM/UNMAP support > 7200 # Rotation rate in RPM > Not_Zoned # Zone Mode > > [root@omega ~]# > From owner-freebsd-fs@freebsd.org Sat Jan 19 19:29:44 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A84614900FB for ; Sat, 19 Jan 2019 19:29:44 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 74BB16A8D5 for ; Sat, 19 Jan 2019 19:29:43 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: by mail-lj1-x22b.google.com with SMTP id t18-v6so14375679ljd.4 for ; Sat, 19 Jan 2019 11:29:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VAL5zjUA+35eiEegGf9IcEuDlKWxGClIybLaJ1yxL9g=; b=JRIYEfIIPtqzT05NntzAGrS6hUZ7plB30HEh/gyH0ZulxJlOTbhYoeAxuIRVxB8cHT M+0jG7oMpQt6gl0YbumMKHXIrDEUyUaDEEuVApensj1hrjuAgeCoEmU1Ylkv/NgawKEx V91rlqcgH+mPf0EyAT5kZzpbPYYkTp6wifcdgQhSZdv064asYbdgJ1AdCj541471lwjD y+DcNt5XkYHS3WHkti6QqXb6UAa3qqDvN7ypF7sw7OLYxxrUAJAHbdd14BlXg8O5pWF9 COUEaVz4pn6UazFZgqXlU/zDsFG2VwmLy2gotpIfTooXEktM9zg8IFnJfaMU57dMiEt5 Ym7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VAL5zjUA+35eiEegGf9IcEuDlKWxGClIybLaJ1yxL9g=; b=mh7xTtqi/kuw8rf64iqS4tDFfYhlTjOeClPShFTSeph6Jsk8B81SDHfCCH0jxwuB6S dmhl3X6X6j5MQ7/0asf2VkA4HMEMDhWhdCGOYJsi0skzZKkGJ9ufkCLpKm8wG/zqfs6Q wNJrV7OJ9mxqVm6eNY6jeiAEQko1jRwh5KaNJL8a+mlbH3uM1GMJDwNoUuowwqmlbIiU YkaeqU0AYZ7MYk2m6/V5SeHGdrlD6NZMCfJUmAyf6g1n7+0LNYl1ImTcBFKjpiZc58VQ Btiu9p/IBNaGAKOYLKM7LRSpoj4xnLJFtVpjHLrOREgqcT0FdTZkvanYc6OaabEbF1Gk JxLw== X-Gm-Message-State: AJcUukceqA5oQY67opiiuzbWaqfNC7hXlKUS4/vYS/5wJgiUVHpiP42X rJSddPemdAodjJ/mTHLRnk5BiEBz3KCRUuUFk/lw4Q== X-Google-Smtp-Source: ALg8bN6oq4coQbPPmm0Y5TTd35IEUXposg3goFzLgokF364fja45NGk0gp8JolP0LEyWjLeKVXogBFZo+rNm0tNCKm4= X-Received: by 2002:a2e:1b47:: with SMTP id b68-v6mr12875904ljb.104.1547926181303; Sat, 19 Jan 2019 11:29:41 -0800 (PST) MIME-Version: 1.0 References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> From: jdelisle Date: Sat, 19 Jan 2019 13:29:29 -0600 Message-ID: Subject: Re: ZFS on Hardware RAID To: Maciej Jan Broniarz Cc: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 74BB16A8D5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=JRIYEfII; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdelisle@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) smtp.mailfrom=jdelisle@gmail.com X-Spamd-Result: default: False [-6.12 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.50)[-0.502,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[b.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.60)[ip: (-9.00), ipnet: 2a00:1450::/32(-2.11), asn: 15169(-1.83), country: US(-0.08)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 19:29:44 -0000 You'll find a lot of strong opinions on this topic over at the FreeNAS forums. I too am wish an authoritative, knowledgeable SME would answer and thoroughly explain the inner workings and the risks involved. Most of the FreeNAS forum posts on this topic devolve into hand-waving and blurry incomplete explanations that end in statements like "trust me, don't do it". I'd love to understand why not. I'm curious and eager to learn more. >From my anecdotal non-expert experience, I ran FreeNAS on 14x 1TB HGST drives as individual RAID0 devices via a SAS HBA that did not support JBOD/ IT mode. This worked very well for me, though I didn't experience drive or controller failure so I can't speak to what would have happened. I created a script that would interrogate the drives' SMART data, and send me a monthly report so I could see trends in their stats. FreeNAS did not support interrogating them for SMART data due to the RAID adapter, but with the correct parameters, smartctl was easily able to so for me. Even though the FreeNAS forum explanations feel incomplete and unsatisfying (to me), I'd suggest following their advice for a production system. For all I know, they may thoroughly understand these inner workings, and just don't feel like (or are bad at) explaining it to the community. Better to be safe than sorry with production data. In my example above, it was just my home lab, and I had very good backups. From owner-freebsd-fs@freebsd.org Sat Jan 19 19:40:21 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C52941490B49 for ; Sat, 19 Jan 2019 19:40:21 +0000 (UTC) (envelope-from ira@wakeful.net) Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A25556B190 for ; Sat, 19 Jan 2019 19:40:20 +0000 (UTC) (envelope-from ira@wakeful.net) Received: by mail-it1-x135.google.com with SMTP id m62so11466019ith.5 for ; Sat, 19 Jan 2019 11:40:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wakeful-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SnRQQz0R1xvlzr6CZOk0NqNjF6cquTm5Zk/lkOKZhfk=; b=AouLRobbCfLWNdax1u/PcFH/hSAJU76Yutq6bAYbxt7UTO69AbCTfROaxDFnim5hbo CRO57ewvJ3DPWDgnQqwGBlcW2pPqomc7C1/rNw3q8wwxXc4cYySC9ACVNnF7vx6ImC6j JO2O1nmhXqSsxvpHBIosuSIp/DdAr6GfauVhuMDBEiBVXjDC+fvw5X7JV7ZhffAlLjHn FeRmZLAasfaLsYC9C907lp4YAvy3j8atH4miwLHFVWay6cELuLkl2k6U1Xeu4krwRk8c 571vFCq6VlCJmaKOnxPHkcZ8pzS+YQiviWuBodq1J6LhRxddmFJhLfOV6kLXCE0uzeJu XnNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SnRQQz0R1xvlzr6CZOk0NqNjF6cquTm5Zk/lkOKZhfk=; b=Jpu20KMTDHfVGy292Vz29xLM+/0KJ9vMvy4Gf/gxUMoV3orfH6ryLHTUhNcr6ndYx3 9Uo3/KBTjiNVJ5xFWqt1lRZR/HzTa+a3Vws7xQpxDcqkwe+PTSUhuNO64yslaDfq32sS wNjmxWCqx9tG6VbxqP/jWl7AWgSliDNJx1qHFPjUuokGgcbSE98YZ2+6Tf/2IodC/fJD KEUIruNlDJB7D5LtxNeZxesaqK2SGgH69CEyhl4Fus0jt40nPEVwria2V4zfaKB7iY6u YRgiHK97QDIQNfRMvtUlqbOMAFmY+iKmGO0PpCxhQqL5a8d/m9CJsgoQAqTj1v6JA60Y qNhA== X-Gm-Message-State: AJcUukeQ3Ti0VNhUff44P9BWv7wnoryHrpRnobcc2j23PT8CjjAznzPk PcUiT8g2Etsy1EZl4fjFMibhywnj+cdTd1OVqio4Z54R X-Google-Smtp-Source: ALg8bN4ziNPxUQIkWFTymJVOEedzRZw3LjdJTV6ZWLXxjNn4BtPjTXxf20VA7C7pAVE5aot6JTgR3sWry0WshJWCIeI= X-Received: by 2002:a24:7609:: with SMTP id z9mr15181975itb.66.1547926819710; Sat, 19 Jan 2019 11:40:19 -0800 (PST) MIME-Version: 1.0 References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> From: Ira Cooper Date: Sat, 19 Jan 2019 14:40:08 -0500 Message-ID: Subject: Re: ZFS on Hardware RAID To: Maciej Jan Broniarz Cc: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: A25556B190 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=wakeful-net.20150623.gappssmtp.com header.s=20150623 header.b=AouLRobb X-Spamd-Result: default: False [-5.34 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[wakeful-net.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[wakeful.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[wakeful-net.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[5.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[ASPMX.L.GOOGLE.COM,ALT2.ASPMX.L.GOOGLE.COM,ASPMX5.GOOGLEMAIL.COM,ALT1.ASPMX.L.GOOGLE.COM,ASPMX3.GOOGLEMAIL.COM,ASPMX2.GOOGLEMAIL.COM,ASPMX4.GOOGLEMAIL.COM]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.55)[-0.550,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.48)[ip: (-8.13), ipnet: 2607:f8b0::/32(-2.37), asn: 15169(-1.83), country: US(-0.08)] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 19:40:22 -0000 On Sat, Jan 19, 2019 at 11:43 AM Maciej Jan Broniarz wrote: > Hi, > > I want to use ZFS on a hardware-raid array. I have no option of making it > JBOD. I know it is best to use ZFS on JBOD, but > that possible in that particular case. My question is - how bad of an idea > is it. I have read very different opinions on that subject, but none of > them seems conclusive. > > Any comments and especially case studies are most welcome. > All best, > I've actually built Illumos based ZFS NAS systems based on raid controllers and non-raid controllers. If given the choice, I'd use non-raid controllers, today. (HBAs) Why? Because ZFS handles the "raid" layer well. The write back cache a RAID controller provides, isn't really needed with ZIL, nor desired. All a raid controller really brings in my experience is added operational complexity once you use good enough hardware, mainly good ZIL drives and HBAs. So it isn't really a "bad" idea, more just redundant, expensive and inconvenient. You could have good reasons to do it, like that the RAID controller is built into the motherboard etc. Just make sure your data integrity is #1. Writeback caches are properly battery protected, or not used. etc. Best, -Ira From owner-freebsd-fs@freebsd.org Sat Jan 19 20:01:02 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8C201491337 for ; Sat, 19 Jan 2019 20:01:02 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 562766BB3F for ; Sat, 19 Jan 2019 20:01:01 +0000 (UTC) (envelope-from jdelisle@gmail.com) Received: by mail-lj1-x244.google.com with SMTP id t18-v6so14407773ljd.4 for ; Sat, 19 Jan 2019 12:01:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Jna/kS4geQAbTPeWI185voZL2QDEtV/29QBWxRd/7iA=; b=UHS/tKKovnmq3ytI7+2hzLw28HoeMG2Wodn0MiwOTSiRrdLTDkRIJzTi4MqFTz/To3 0HhXGVH7XruK34ppHWNiVF93VSiYq/Aidds+2WSpdtkQflJKxRzdUZR9/04lD4QbM53H uxkZsQxhdhPGNoWHvUksSvVvSKsOTkD/OM8eVT9c0xBbm8MTa2aF1UdttwcscFNufqIM cbuq7TfS0e2tLWRRNeJUyRETOYVTZ+8ClXFfZYJnmOihaQDTTkrUOSYXKxm2SVngLyGa KcyrwPeD8ROD3D1zvR+1uj7+oWFnUHZ3xI7CjzqnKUEthvnA5F5EM+e9nvUgJ1esqXe9 Po3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Jna/kS4geQAbTPeWI185voZL2QDEtV/29QBWxRd/7iA=; b=qF8Gu56g4NWf1ILP8WYdyRdsoa1ulCinFFHv8b8DCoJA0OTqr00EqUbZyVgbTdtLon RlN6Fgv2jxLrDN8c7SPve1TifzOiiYJDbnx5frgEPqWOYFS/DhnHF/WylFcTtzk0tlLz mJnzs7N3owBoe+Vhe7HnfkvqZ4AW79NnaBXD+l3bBnqGevxgblyXGD7e0p6el/BCrNp0 NVxn4I2dPjHdRM7t0rnDWk/jP1/KNiYNqSDI7uijWD3kHKcpxPrCHne7CIiK9n3F5YHq OpIdY5CGjEDm2QF8uPhCVrmvL2rmcqhfkhzXG56BVdphg8udshjE/2xTb+Uo+fNjzAEY QrpA== X-Gm-Message-State: AJcUukd3I93ZkGdHjX0i/mSQ8VXaEa6i7SUF5kdTUX9xIgvLAliimQMv iiZS/dQon0/unyolPpcLm9Hy+3cMzskPfBvdGx0= X-Google-Smtp-Source: ALg8bN6UtyFIIe/A+kFsy1KlogSsQAcEAAEO/5Xj+3LBskSAl/ySBrR0lrWPk9zpMHHucbhZFd0T1N8VxujVr0heH60= X-Received: by 2002:a2e:1b47:: with SMTP id b68-v6mr12902545ljb.104.1547928059724; Sat, 19 Jan 2019 12:00:59 -0800 (PST) MIME-Version: 1.0 References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: From: jdelisle Date: Sat, 19 Jan 2019 14:00:47 -0600 Message-ID: Subject: Re: ZFS on Hardware RAID To: Ira Cooper Cc: Maciej Jan Broniarz , freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 562766BB3F X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=UHS/tKKo; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdelisle@gmail.com designates 2a00:1450:4864:20::244 as permitted sender) smtp.mailfrom=jdelisle@gmail.com X-Spamd-Result: default: False [-3.45 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[4.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-0.13)[-0.134,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.30)[ip: (2.50), ipnet: 2a00:1450::/32(-2.11), asn: 15169(-1.83), country: US(-0.08)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 20:01:03 -0000 Wouldn't a write-back cache (battery-backed) improve write performance? Assuming the cache is sufficiently sized for the workload, would it not have an effect similar to ZIL, meaning low-latency persisted writes? On Sat, Jan 19, 2019 at 1:41 PM Ira Cooper wrote: > On Sat, Jan 19, 2019 at 11:43 AM Maciej Jan Broniarz > wrote: > > > Hi, > > > > I want to use ZFS on a hardware-raid array. I have no option of making it > > JBOD. I know it is best to use ZFS on JBOD, but > > that possible in that particular case. My question is - how bad of an > idea > > is it. I have read very different opinions on that subject, but none of > > them seems conclusive. > > > > Any comments and especially case studies are most welcome. > > All best, > > > > I've actually built Illumos based ZFS NAS systems based on raid controllers > and non-raid controllers. > > If given the choice, I'd use non-raid controllers, today. (HBAs) > > Why? Because ZFS handles the "raid" layer well. The write back cache a > RAID controller provides, isn't really needed with ZIL, nor desired. > > All a raid controller really brings in my experience is added operational > complexity once you use good enough hardware, mainly good ZIL drives and > HBAs. > > So it isn't really a "bad" idea, more just redundant, expensive and > inconvenient. You could have good reasons to do it, like that the RAID > controller is built into the motherboard etc. > > Just make sure your data integrity is #1. Writeback caches are properly > battery protected, or not used. etc. > > Best, > > -Ira > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Sat Jan 19 20:08:45 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1E5C1491951 for ; Sat, 19 Jan 2019 20:08:44 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA8F6C2DE for ; Sat, 19 Jan 2019 20:08:43 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-lj1-x22f.google.com with SMTP id n18-v6so14398559lji.7 for ; Sat, 19 Jan 2019 12:08:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CSFDy1/jOEmRbXWOJBwj8EZNiqLZ947YyqOUYhXQe9M=; b=jtCkmaexbBYoNOaSeKvUCANomlKA2K2DGzjciYBZCGA6OM8Mjt0YEuT1MT8rsSuP96 q2DsgWRS2rTSlV0oeiZD946KoY5RTI4rvs7l4qM25ulXs2EUv1Z7bA74dY3MXJL7DoMN uN/WtPSbKei5cfA8Hoo3fuwr6aTihd/q5nTlYfhMfm04gNYTkXFWkL0+sTQlNr4noEhE Gp396W1mWuvI627fXAYvQoczHD+J1w5zAAR+Ard7lvvghieXL9xoUGSeh78qKVl4NmXP GkuBhrlOUhCJXjN82deiUPyPqS4YwVI3lKAKwxe/Z70dT/fqnWax3o8OKosV3XrACEaA hCHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CSFDy1/jOEmRbXWOJBwj8EZNiqLZ947YyqOUYhXQe9M=; b=s2Xbd/Y8Ph/E67ah0RmrSakaXA6DMG9X8/XHZi+pRBpZrN0iFs5NDdPUxzuxey8TcV 9H3HY5uHUsXwR+iYZhr1/Yk3lvPK3AP5LDy5etPRbq3Hn6sqN1iKS/Bpmp+CN4ZyDeFj gYCgfOwwsXTSJFu+sOzOPFqVp9bj+sYbdwBIZosKSFLZL42gimrBpxvO0K2CGhM/n0Fu K0s75zgUZYO6iRROq1ER6KW8d0lE6nVr5UaaESWvqcDat8ks8CU5KSg9+tc/SX/RbqG6 poiZ+cL4LTm3psY9xdYrQgAIpCau43McD3RgTC7Y0AzELxqPrk58BMWYSv3F5gvITaQP 1dgA== X-Gm-Message-State: AJcUukf4SXzD+qaHKNgQdzVB8hCQgIA1TPQ7zbIw6LUmGqC4ysae34yd gmehHrkM6Agv4fqczsQsrYMWMY9b1+ZqOpmzpgQ5OQ== X-Google-Smtp-Source: ALg8bN5aTE4uYWOXjhGQviD7aSDWRWvZUN4ZVI7K+Eth5eqM/0qVb1Ne99KGhS7d29boztih9OyweNbmA65+E4WIVKQ= X-Received: by 2002:a2e:880a:: with SMTP id x10-v6mr15993950ljh.174.1547928521385; Sat, 19 Jan 2019 12:08:41 -0800 (PST) MIME-Version: 1.0 References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> From: Rich Date: Sat, 19 Jan 2019 15:08:29 -0500 Message-ID: Subject: Re: ZFS on Hardware RAID To: Maciej Jan Broniarz Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 2DA8F6C2DE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=jtCkmaex; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rincebrain@gmail.com designates 2a00:1450:4864:20::22f as permitted sender) smtp.mailfrom=rincebrain@gmail.com X-Spamd-Result: default: False [-6.57 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.86)[-0.863,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[f.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.69)[ip: (-9.44), ipnet: 2a00:1450::/32(-2.11), asn: 15169(-1.83), country: US(-0.08)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 20:08:45 -0000 The two caveats I'd offer are: - RAID controllers add an opaque complexity layer if you have problems - e.g. if you're using single-disk RAID0s to make a RAID controller pretend to be an HBA, if the disk starts misbehaving, you have an additional layer of behavior (how the RAID controller interprets drives misbehaving and shows that to the OS) to figure out whether the drive is bad, the connection is loose, the controller is bad, ... - abstracting the redundancy away from ZFS means that ZFS can't recover if it knows there's a problem but the underlying RAID controller doesn't - that is, say you made a RAID-6, and ZFS sees some block fail checksum. There's not a way to say "hey that block was wrong, try that read again with different disks" to the controller, so you're just sad at data loss on your nominally "redundant" array. - Rich On Sat, Jan 19, 2019 at 11:44 AM Maciej Jan Broniarz wrote: > > Hi, > > I want to use ZFS on a hardware-raid array. I have no option of making it JBOD. I know it is best to use ZFS on JBOD, but > that possible in that particular case. My question is - how bad of an idea is it. I have read very different opinions on that subject, but none of them seems conclusive. > > Any comments and especially case studies are most welcome. > All best, > mjb > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Sat Jan 19 20:15:17 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFBE414931BE for ; Sat, 19 Jan 2019 20:15:17 +0000 (UTC) (envelope-from ira@wakeful.net) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC1686CB54 for ; Sat, 19 Jan 2019 20:15:16 +0000 (UTC) (envelope-from ira@wakeful.net) Received: by mail-io1-xd2e.google.com with SMTP id c2so13542964iom.12 for ; Sat, 19 Jan 2019 12:15:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wakeful-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LkWo9cbvk5ar+SjQv7yr9itfx+u+GhEukrmbOzQeZPk=; b=iDiWNi0cJ4wXo4S5pwhUjIH40BwPWZWcVcCPOs/jq27aIK52Tvn5UsKyMtV+2p1/zw 2ogxgtrkBZPJkQnQsjsRg9M9I5dnIyLjfZp+eaAzsSVPQ7ePfxFahs5DIS2M1X7AmszN QCLZnvMBxNB5uNxmeOPnc33OSyVW8pjB1a8lE8zoMYJBJ4RPbuGA5ayO7t5SRWkrC1RF fo2CvoFyTshIcU/ITdEvLO8vB1asI5yoLIpGFRq69z7YdxHxWIWIutwR1Rd6BOL6ikEK 0y9wQxQI0Uq9LfnGMOSgtK5ZVaV/RpBFNZeZwfwQI7xevYlgf90GmxZng0hQ8WeWg48I pKNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LkWo9cbvk5ar+SjQv7yr9itfx+u+GhEukrmbOzQeZPk=; b=aD40xnTNyriDmR2/7/EV45ZGYOzRch5StQr6k5R4Wku1BVRlityWO8JW8BKsdjfiyn S8ClhGaifT0m7S+sBaEDywOXDMBnzX5WQaMeUs8z66kQrxbbn1UCNTSeThRZE+I2jEb/ kPoyGJAM3p9XEQJbeXtuME/JbA7bvSLtj4Y/0Z3V/9FUSJSyZqfYNSeB5KPKU5eq81Nk Fuv7NNZDZ5tHYnM+v0sjguSbnSLbSgPRmgD+PFHM1f96ftsaJ5jfX9alCghHBy/+ANr7 EkvU9uEBNNwc6FuRZ8+I93+gVidMGOIuD0MG7fmU5+gX74hVuYJQ8PMDzmg1aUSkHbql eH9w== X-Gm-Message-State: AJcUukeVr8Tmr4Ta3wzRs3vfDQoKBtq20uq8BUfR13xugMm5AKmiYfKp Y4vDRIWZSKAlNjwIfNnOvzJF26LmjcTlAAtP2agkFg== X-Google-Smtp-Source: ALg8bN54kLyv1o7DZ+BKxxn6eSEQB+gMwIaPHPExuHVIo0S3T+/BcxXLLfBwtt0iu5E+2k+GI9vg56Lbw1O12267pA0= X-Received: by 2002:a6b:e00e:: with SMTP id z14mr12366748iog.264.1547928915881; Sat, 19 Jan 2019 12:15:15 -0800 (PST) MIME-Version: 1.0 References: <1180280695.63420.1547910313494.JavaMail.zimbra@gausus.net> <92646202.63422.1547910433715.JavaMail.zimbra@gausus.net> In-Reply-To: From: Ira Cooper Date: Sat, 19 Jan 2019 15:15:05 -0500 Message-ID: Subject: Re: ZFS on Hardware RAID To: Rich Cc: Maciej Jan Broniarz , freebsd-fs X-Rspamd-Queue-Id: AC1686CB54 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=wakeful-net.20150623.gappssmtp.com header.s=20150623 header.b=iDiWNi0c X-Spamd-Result: default: False [-5.56 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[wakeful-net.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[wakeful.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[wakeful-net.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ASPMX.L.GOOGLE.COM]; RCVD_IN_DNSWL_NONE(0.00)[e.2.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.90)[-0.904,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.34)[ip: (-7.43), ipnet: 2607:f8b0::/32(-2.37), asn: 15169(-1.83), country: US(-0.08)] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 20:15:18 -0000 Well put. In addition, by using a raid controller, you are likely depriving the OS and ZFS the ability to use the drive's writeback caches, and queue depth management. Cheers, -Ira On Sat, Jan 19, 2019 at 3:09 PM Rich wrote: > The two caveats I'd offer are: > - RAID controllers add an opaque complexity layer if you have problems > - e.g. if you're using single-disk RAID0s to make a RAID controller > pretend to be an HBA, if the disk starts misbehaving, you have an > additional layer of behavior (how the RAID controller interprets > drives misbehaving and shows that to the OS) to figure out whether the > drive is bad, the connection is loose, the controller is bad, ... > - abstracting the redundancy away from ZFS means that ZFS can't > recover if it knows there's a problem but the underlying RAID > controller doesn't - that is, say you made a RAID-6, and ZFS sees some > block fail checksum. There's not a way to say "hey that block was > wrong, try that read again with different disks" to the controller, so > you're just sad at data loss on your nominally "redundant" array. > > - Rich > > On Sat, Jan 19, 2019 at 11:44 AM Maciej Jan Broniarz > wrote: > > > > Hi, > > > > I want to use ZFS on a hardware-raid array. I have no option of making > it JBOD. I know it is best to use ZFS on JBOD, but > > that possible in that particular case. My question is - how bad of an > idea is it. I have read very different opinions on that subject, but none > of them seems conclusive. > > > > Any comments and especially case studies are most welcome. > > All best, > > mjb > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Sat Jan 19 21:08:20 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65B921494EA9 for ; Sat, 19 Jan 2019 21:08:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F23266FA3A for ; Sat, 19 Jan 2019 21:08:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id ABD921494EA8; Sat, 19 Jan 2019 21:08:19 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 988061494EA6 for ; Sat, 19 Jan 2019 21:08:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E8F76FA38 for ; Sat, 19 Jan 2019 21:08:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6C70A11A69 for ; Sat, 19 Jan 2019 21:08:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0JL8IL6093093 for ; Sat, 19 Jan 2019 21:08:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0JL8IER093081 for fs@FreeBSD.org; Sat, 19 Jan 2019 21:08:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229958] ctld / zfs deadlock with 'zfs rename ...' Date: Sat, 19 Jan 2019 21:08:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mlavkin@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2019 21:08:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229958 mlavkin@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlavkin@gmail.com --- Comment #11 from mlavkin@gmail.com --- Have same problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226499 --=20 You are receiving this mail because: You are the assignee for the bug.=