Date: Fri, 15 Jun 2007 11:14:09 -0400 From: "Ali Mashtizadeh" <mashtizadeh@gmail.com> To: "Claus Guttesen" <kometen@gmail.com> Cc: freebsd-current@freebsd.org, Benjamin Close <Benjamin.Close@clearchain.com> Subject: Re: Swapfile on ZFS & Deadlock Message-ID: <440b3e930706150814s48ea3750k2ca1ea395a14bad0@mail.gmail.com> In-Reply-To: <b41c75520706150745w6929c24dq3bf86a204d47b1f9@mail.gmail.com> References: <4672945C.3060304@clearchain.com> <b41c75520706150745w6929c24dq3bf86a204d47b1f9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've had a similar thing when I'm using a lot of swap on ZFS then sometimes the strain on memory resources brings my system to a crawl I can't get out of :(. But it only happends on systems with less than 1 GB of memory. It's not actually crashed -- Ali Mashtizadeh علی مشتی زاده On 6/15/07, Claus Guttesen <kometen@gmail.com> wrote: > > > Whilst running out of memory compiling Xorg (scanPCI is a killer) I > > discovered a quick way to deadlock the system: > > > > dd if=/dev/zero of=somefileonzfs bs=something count=something > > mdconfig -a -f something > > swapon /dev/md0 > > > > Then do something that needs swap.. instant deadlock. The system is > > still responsive but all disk access become hung. > > > > Known issue? If so is there a way we can warn users/prevent users from > > doing it? > > How much swap have you allocated? > > -- > regards > Claus > > When lenity and cruelty play for a kingdom, > the gentlest gamester is the soonest winner. > > Shakespeare > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440b3e930706150814s48ea3750k2ca1ea395a14bad0>