> On Apr 12, 2020, at 01:48, Eugene Grosbein wrote:
>
> There is very simple way to prevent such problem, use: zfs set reservation=1G
> for single "root" file system of the pool.
>
> This way ZFS won't allow applications to fill the pool to the point it starts
> crawling.
> Instead, writing a
> On Apr 11, 2020, at 14:33, Eugene Grosbein wrote:
>
> 12.04.2020 0:36, Chris Ross wrote:
>
>> I have a FreeBSD 11.3-STABLE server that is my router, using a ZFS mirror
>> (of two GPT disks) as it’s disk. It’s many years old, and has only been
>> misbehaving l
I have a FreeBSD 11.3-STABLE server that is my router, using a ZFS mirror (of
two GPT disks) as it’s disk. It’s many years old, and has only been
misbehaving like this for a day or so. I’m trying to figure out what’s wrong.
I confirmed that internet connectivity isn’t the problem, and a reboot
> On Nov 9, 2019, at 16:07, Toomas Soome wrote:
>> On 9. Nov 2019, at 22:42, Chris Ross wrote:
>>
>> On Sat, Nov 09, 2019 at 11:24:49AM -0600, Kyle Evans wrote:
>>> Hi,
>>>
>>> That helps- thanks! I'm CC'ing tsoome@, as this is
On Sat, Nov 09, 2019 at 04:51:38PM -0500, Chris Ross wrote:
> > > Can you provide some guidance of what I need to do to get the mrsas
> > > driver to identify it when booting the install ISO?
> >
> > See the "PRIORITY" section of
> >
> > https
On Sat, Nov 09, 2019 at 04:48:10PM +, Gary Palmer wrote:
> > Hi Doug! Thanks. Okay, I infer from that that the mpr driver is for
> > HBAs that aren't raid? Grepping through the sources for 3516 found me
> > only mpr. Looking more carefully, at mrsas while knowing specifically
> > what I'm l
On Sat, Nov 09, 2019 at 11:24:49AM -0600, Kyle Evans wrote:
> Hi,
>
> That helps- thanks! I'm CC'ing tsoome@, as this is basically just
> r353501 in that range. Can you give the latest -CURRENT snapshot boot
> as another data point?
Thanks. And yeah, happily, I was already in the process of buil
On Thu, Nov 07, 2019 at 02:53:25PM -0500, Chris Ross wrote:
> > > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote:
> > >> You could try some bisection back along the 12 branch..
>
> Yeah. I was hoping for an easier path, but. I can try slogging back
> throu
On Fri, Nov 08, 2019 at 02:28:17PM -0800, Doug Ambrisko wrote:
> On Tue, Nov 05, 2019 at 09:44:36PM +0100, Miroslav Lachman wrote:
> | Chris Ross wrote on 11/05/2019 21:19:
> | > On Tue, Nov 05, 2019 at 08:20:15PM +0100, Miroslav Lachman wrote:
> | >> Chris Ross wrot
On Thu, Nov 07, 2019 at 10:56:00AM +1000, George Michaelson wrote:
> On Thu, Nov 7, 2019 at 10:21 AM Julian Elischer wrote:
> >
> > I suspect a separate bug because the OP specified that it worked in
> > 12.0 where those bugs go back to 9.x
>
> Oh, I didn't realize I updated a PXE boot PR. I am
On Tue, Nov 05, 2019 at 05:04:41PM -0500, Chris Ross wrote:
> > However, if you've already placed
> > mpr_load="YES" in your /etc/loader.conf and rebooted your device, then you
> > probably need to move into a diagnostic phase.
>
> Yeah. I think I see what
On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote:
>
> Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system
> here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso
> did work on that same system. [Systems were configure
Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system
here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso
did work on that same system. Another [older] system I had was working with
FreeBSD-12.1-RELEASE-amd64-disc1.iso, but after I had reason to c
On Wed, Nov 06, 2019 at 08:44:35AM +1100, Dewayne Geraghty wrote:
> Chris,
> After you've booted the kernel, the correct way to load a module that isn't
> already in the kernel, is to:
> kldload mpr
> To check if mpr is loaded, try
> kldstat -v|grep mpr
Thanks for this. I was able to boot and ver
On Tue, Nov 05, 2019 at 12:29:00PM -0800, Freddie Cash wrote:
> > I tried "load", but wasn't able to devine how to load the mpr module with
> > that. Is that needed, or should 'mpr_load="YES"' have accomplished the
> > desired result?
>
> modulename_load="YES" is the syntax used in the loader.con
On Tue, Nov 05, 2019 at 08:20:15PM +0100, Miroslav Lachman wrote:
> Chris Ross wrote on 11/05/2019 19:34:
> > Hello. I have a Cisco UCS C220-M5 with a RAID controller. It calls itself
> > "Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5.
> > Lo
Hello. I have a Cisco UCS C220-M5 with a RAID controller. It calls itself
"Cisco 12G Modular Raid Controller with 2GB cache", PPID UCSC-RAID-M5.
Looking at the CIMC, it shows the PCI vendor/device ids 1000:0014, which
looks to be an LSI MegaRAID Tri-Mode SAS3516. It looks like this should
be sup
> On Jul 3, 2017, at 14:46, Kurt Jaeger wrote:
>
> Use __FreeBSD_version from sys/param.h:
>
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html
Thanks. That looks great. Also, for my specific case of the addition of
clock_nanosleep(), it looks from time.h l
Some time ago, I ported a linux program that was using clock_nanosleep(). I
see now that the extra code I’d put in isn’t needed anymore in 11-stable, as it
appears this call was added in 11.1. My question is, to properly protect these
changes, what is the best way to know at compile time, e
> On Jul 1, 2015, at 11:34, Kurt Lidl wrote:
> I discovered that if I comment out the following lines
> from my /etc/rc.conf, the machine boots reliably:
>
> ifconfig_bge0="DHCP"
> ifconfig_bge0_ipv6="inet6 accept_rtadv"
>
> Of course, with no network connection, it's not a very useful machine,
On Jul 1, 2015, at 05:18 , Fabian Keil wrote:
> Does it make a difference if you boot with hw.bge.allow_asf=0?
>
> According to the man page it is known to "cause system lockup problems
> on a small number of systems". It's not obvious to me why it's enabled
> by default on FreeBSD and I disable
On Jun 30, 2015, at 22:36 , Glen Barber wrote:
> On Tue, Jun 30, 2015 at 10:27:21PM -0400, Chris Ross wrote:
>>
>> Yeah, this is the same panic you, I, and others have been seeing on
>> sparc64's
>> with bge's, or at least v240's (and one other IIRC
Yeah, this is the same panic you, I, and others have been seeing on sparc64's
with bge's, or at least v240's (and one other IIRC) for many many months.
Thanks
for grabbing a core!
When I was trying to search for a commit that caused the change of behavior,
I had difficultly doing it, but it
On Apr 21, 2015, at 10:10 , Gareth Wyn Roberts
wrote:
> This may be caused by DMA alignment problems.
> See
> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=145859+0+archive/2015/freebsd-stable/20150419.freebsd-stable
> for a recent thread about the msk driver. The msk maintainer Yonghyeon Pyu
I got a new [to me] system recently, a Dell PE 1950. It has two bce parts on
the motherboard that identify as:
bce#:
The OS I installed and kernel I'm running are from a download of a 10.1
STABLE ISO, r281235, April 7, 2015.
I had gone on to check out a newer stable from subversion, a
On Jul 30, 2013, at 10:07 , Mark Felder wrote:
> On Tue, Jul 30, 2013, at 8:42, sth...@nethelp.no wrote:
>>
>> and every contrib part which is removed, detracts from this.
>
> And every contrib part that is added to base is another piece of
> software that rots for the life of a major release an
On Jul 1, 2013, at 22:30 , Chris Ross wrote:
> Maybe I messed something up in the kernel I was building. Let me drop back
> to a GENERIC
> from the same stable/9 and see if that will boot. I just have to figure out
> how to get it onto the
> disks. :-)
User error. Thanks
On Mon Jul 1 19:51:45 UTC 2013, Gary Palmer wrote:
> What is the interface that the disk(s) that ZFS are on? If it's the
> AcerLabs ATA controller, then there are no disks found. There is an
> earlier ATA bus (at a guess from the fact ata2 and ata3 are shown above),
> however I don't see any d
I had a sparc64 (Netra X1) running a stable/9 from late March 2013.
Actually, the kernel may've been a bit newer than that as I was working with
folks to diagnose and repair some Netra-X1 specific issues. But, ZFS worked
fine. I have two pools, zroot as a RAID1 (using equally sized partiti
On May 12, 2013, at 23:17 , Jeremy Chadwick wrote:
> On Sun, May 12, 2013 at 10:20:26PM -0400, Chris Ross wrote:
>> In the past, I've found I've been unable to install all of the bootblocks if
>> I
>> boot from the ZFS root. When booting from a cd, the basic
On May 12, 2013, at 16:58 , Jeremy Chadwick wrote:
> The command is "gpart bootcode", however I cannot be bothered to
> remember the syntax; I imagine it greatly depends on if you're using GPT
> vs. MBR, in addition to what your partition layout look like. Meaning:
> there is no "universal stand
So, I've long known and it makes sense that when you're booted from a ZFS
volume, you can't mess with the boot-loader. And, I know a few months ago I
had a set of commands I would use when booted from a CD that would initialize
the network and copy the "release/boot" from somewhere else so t
013 1:17:41 pm Chris Ross wrote:
>>
>> So, I was looking at a v240 I have running stable/9 (9.1-STABLE), and
>> noticed something odd. The per-CPU information displayed by top seems
>> inconsistent. To simplify things, while I'm running a "make release&quo
33 matches
Mail list logo
