Date: Sat, 11 Jun 2016 17:57:13 -0400 From: Warner Losh <imp@bsdimp.com> To: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com> Cc: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: smartmontools now broken on -current (by svn r301771, r301778?) Message-ID: <CANCZdfodZ3FYbMCreofrJxLuKmw8CxjJfkLqDgSW_YZ3_YiC6g@mail.gmail.com> In-Reply-To: <683CEA47-277C-4467-86D1-DA6C4ED8D4AE@gmail.com> References: <d189013a-28bc-a31e-928e-5068f1b65c45@protected-networks.net> <683CEA47-277C-4467-86D1-DA6C4ED8D4AE@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm skeptical. The ATA stuff isn't anything that I've committed to, so that isn't new. The nvme stuff is because smartmontools defines nvme stuff that conflicts with the FreeBSD defines... Warner On Sat, Jun 11, 2016 at 9:42 AM, Ngie Cooper (yaneurabeya) <yaneurabeya@gmail.com> wrote: > >> On Jun 11, 2016, at 09:40, Michael Butler <imb@protected-networks.net> w= rote: >> >> The recent nvme updates have broken smartmontools .. >> >> imb@toshi:/home/imb> sudo smartctl -a /dev/ada0 >> smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build) >> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.= org >> >> /dev/ada0: Inappropriate ioctl for device >> Please specify device type with the -d option. >> >> Attempts to recompile the utility also fail: > > Hi Michael, > Please file a bug =E2=80=94 in ports first, and if necessary in t= he base system. > Thank you! > -Ngie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfodZ3FYbMCreofrJxLuKmw8CxjJfkLqDgSW_YZ3_YiC6g>