Re: FreeBSD mbufs() cache poisoning local priv escalation v2 by KCOPE
On 24.08.2011 16:59, Victor Detoni wrote: > Does Someone know if this was fixed? > > On Wed, Aug 24, 2011 at 11:57 AM, Victor Detoni wrote: > >> Oh shit guys! >> >> http://pastebin.com/dyKLRr0v >> http://security.freebsd.org/advisories/FreeBSD-SA-10:07.mbuf.asc Isn't this the one? //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm
On 21.07.2010 18:33, Ståle Kristoffersen wrote: > On 2010-07-20 at 14:16, Svein Skogen (Listmail account) wrote: >> Sorry for the late response here, but what you're describing matches >> fairly well what I saw with RELENG_8 (just after 8.0 was released), but >> luckily I didn't have any disks on my MPT, just my tape autoloader. >> >> Random timeouts, and then bus resets (that made tape IO unreliable). >> >> The bad news, is that I had the exact same trouble with OpenSolaris >> (134), and something-similar with Linux (can't remember versions), at >> the time. >> >> I never did find a solution, and ended up throwing windows on the box, >> just to get reliable backups. >> >> My MPT is a 3801 LSI1068e based card running the latest bios. > > Hmm, that does not sound good. Did windows work on the same hardware > without problems? Yup. But notice that I do _NOT_ have any disks on my MPT (I have an MFI for that), it's just a mini-sas<-->mini-sas into a HP 1/8G2 LTO3 Autoloader. > I -might- have solved my problem. It has now ran for 24h without timeouts, > and with a bit of load on it. I think I might have ran into the seagate + > NCQ-problem, even tho seagate's webpage told me my drives was not affected > (according to the serial numbers). I did however update the following > num drives firmware > 6x ST31000340AS SD15 > 4x ST31500341AS SD17 I have 8 of the last type (31500341AS) mine running on CC1H firmware, connected to my MFI. Not a single glitch so far. > > to firmware SD1B (old SD17) and SD1A (old SD15), and that looks like it has > done the trick. I'll report back in a week or so if the problem has not > reappeared. Hope it's fixed for you. I'm still keeping an eye on the MPT code to see if someone changes something that CAN be affecting my timeout issues/reset, and if I see something promising, I'm willing to dump out the entire server to tapes, and test run (I have sufficient spare tapes to actually test without losing data), but such a job will take me a week to prepare, and another to test. Quite a bit of time for something that "may" solve my problem... ;) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm
On 20.07.2010 13:55, Ståle Kristoffersen wrote: > On 2010-07-20 at 12:17, Marius Strobl wrote: >> On Mon, Jul 19, 2010 at 07:06:54PM +0200, Stle Kristoffersen wrote: >>> On 2010-07-18 at 14:20, Marius Strobl wrote: >> Downgrading now... > > And it crashed again, with current from r209598... > Ok, this at least means that your problem isn't caused by the recent changes to mpt(4) as the pre-r209599 version only differed from the 8-STABLE one in a cosmetic change at that time. >>> >>> I have another data-point, I cvsup'ed to the latest current again, and >>> rebuilt without INVARIANT and WITNESS, and now it seems to survive the >>> timeouts. >> >> That's more or less expected as the sanity check issuing the panic >> just isn't compiled in then. However, my understanding was that with >> STABLE you don't get the timeouts in the first place, or do you see >> them there also? > > I got the timeouts with STABLE as well, that was the reason for me to > try out CURRENT. I'm sorry I didn't mention that earlier. > > My main concern is to get rid of the timeouts, but a panic on one can't be > right. How can I debug this further? I can get timeout fairly consistent by > putting a bit of load on the drives. If it would help I can also provide > remote access. > > I'm trying to update the firmware on some of the drives now to see if that > helps with the timeouts. Sorry for the late response here, but what you're describing matches fairly well what I saw with RELENG_8 (just after 8.0 was released), but luckily I didn't have any disks on my MPT, just my tape autoloader. Random timeouts, and then bus resets (that made tape IO unreliable). The bad news, is that I had the exact same trouble with OpenSolaris (134), and something-similar with Linux (can't remember versions), at the time. I never did find a solution, and ended up throwing windows on the box, just to get reliable backups. My MPT is a 3801 LSI1068e based card running the latest bios. //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: Dell Perc 5/i Performance issues
On 19.06.2010 11:58, oizs wrote: > I tried almost everything raid 0 1 5 10 with all kind of stripes > 32/64/128 and settings direct io/cached/read-ahead/wt/wb/disk-cache but > nothing seems to work. > I changed the card to another dell perc 5 which had an older firmware. > Tried 4 kind of motherboards even tried changing the os to linux and > windows xp/7. In windows I got some funny results 1.3MB/s with > write-back and 150MB/s reads with 5 disks in raid0. > I just wanted to have a hw raid with no problems since the motherboard > 88sx7042 and bsd did not like eachother. This is from a similar controller running that 8-disk raid5+0 setup: -- CrystalDiskMark 2.2 (C) 2007-2008 hiyohiyo Crystal Dew World : http://crystalmark.info/ -- Sequential Read : 665.383 MB/s Sequential Write : 300.452 MB/s Random Read 512KB : 616.604 MB/s Random Write 512KB : 306.306 MB/s Random Read 4KB : 64.465 MB/s Random Write 4KB :7.646 MB/s Test Size : 100 MB Date : 2010/06/19 14:24:12 You should be looking at number about half of these. I ran the test with adaptive readahead enabled, and write-through for cache (since I run with BBU, I normally use write-back) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: Dell Perc 5/i Performance issues
On 18.06.2010 01:50, oizs wrote: > Hi, > > I've bought a Dell Perc 5/i because I couldn't make the onboard marvell > 88sx7042 work with 8.0/8.1 or current, but as lucky as I am, the best I > can do with 4x1.5tb samsung in raid5 is 60MB/s writes and 90MB/s reads, > with bbu/write-back/adaptive-read-ahead. > > I was expecting at least twice of that, and I'm not sure what can I do > to get that speed. (I've read man 7 tuning with no success) > > As far as I know this controller should be as fast as on other systems. > (Freebsd.org mx1 has one of these cards.) > > I'm hoping somebody on the list reads this and helps because I can't > afford to buy another card. I've lost track of what actual boards Dell has OEMized to make the various PERCs, but if I remember somewhat correctly, the PERC5 is basically an LSI Megaraid SAS 8308elp with different labels and firmware? If so, I've got that exact controller (minus the dell labels and firmware) in my primary storage box here, and yes, you SHOULD be able to get more performance out of it. What's your strip sizes and logical disk layout? (I've got the same board running on 8x 1T5 Seagates in RAID5+0, and that setup easily pulls 5 times the values you're seeing, and by all logic you should see about half of what I'm seeing) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: RFC: etcupdate tool in base?
On 12.06.2010 14:57, Sam Fourman Jr. wrote: > On Thu, Jun 10, 2010 at 1:14 PM, Joel Dahl wrote: >> On 10-06-2010 13:46, John Baldwin wrote: >>> I've had several folks ask me recently about importing etcupdate >>> (http://www.FreeBSD.org/~jhb/etcupdate) into the base system as an alternate >>> tool for updating /etc during upgrades. Do folks have any strong objections >>> to doing so? More details about how it works and an HTML version of the >>> manpage can be found at the URL above. >> >> +1 for importing it into base. >> > +1 for importing into base. > I would use it. And another +1 from me. It solves a problem that needs solving. (and yes, I would use it) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD
On 01.06.2010 20:57, Vanessa Kraus wrote: > It's exciting that there may soon be an option other than gcc for > FreeBSD. However I have a few questions. Is there going to be a system > in place that will allow port maintainers to say "hey this port is now > built successfully with Clang" or "hey this port only builds > successfully with gcc"? Is it realistic to think that gnome and kde > could be built with Clang/LLVM now or in the future? Do you know when > you will be interested in being notified of arbitrary ports that wont > build with Clang, and where should these notifications be sent? Actually, such a system kind of already exists. It's called "build-depends" ;) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD
On 01.06.2010 16:55, Dag-Erling Smørgrav wrote: > Attilio Rao writes: >> I really would like to see CLANG more integrated with FreeBSD only >> when there are 0 or similar (well-known, already analyzed, listed >> somewhere, etc.) bugs by the compiler [...] > > Does this means you're planning to remove GCC, since it has tons of > known bugs? Sounds more like a knee-jerk reaction to removal of GCC by a ... herd of gnus. ;) //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: [RFC] Rewriting sade(8)
On 08.04.2010 11:05, Dag-Erling Smørgrav wrote: > Alexander Leidinger writes: >> Please consider using SVN instead. A lot more users will be able to >> check out from there. > > We don't grant non-committers access to the Subversion repo. > >> It looks like other people had a look at sysinstall, not at sade. As >> sysinstall is supposed to be used at installation time, and the intent >> for sade was to offer the functionality (or more) of the part of >> sysinstall which is useful after installation (and to prevent admins >> from using sysinstall after the installation to prevent some unwanted >> foot-shooting), I do not think that we need to think about a strong >> lock between sysinstall and sade. > > Yes we do. Otherwise we'll just end up back where we are today, where > if you want anything more complicated than a single-disk install you > have to drop into the fixit shell and do it manually before running the > installation procedure. Anythig that sade can do, we want sysinstall to > do as well, and we don't want to implement everything twice. > > My suggestion is to add a "sysinstall mode" to sade where it operates > under certain (minor) constraints and reports what it did in a format > that sysinstall can parse, so sysinstall can just fork-exec sade instead > of duplicating the code. Wouldn't a setup similar to fetch/libfetch do the trick here? Move most of the actual "working payload" of sade into a library, and make sade just a frontend for this? That way poking the sysinstall code to use sade should be easier, and updates will automagically fix both things? //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.03.2010 01:49, Carlos A. M. dos Santos wrote: > On Tue, Mar 23, 2010 at 8:39 PM, jhell wrote: >> >> On Mon, 22 Mar 2010 15:42, deischen@ wrote: >>> >>> [ Some CC's stripped ] >>> >>> On Mon, 22 Mar 2010, M. Warner Losh wrote: >>> P.S. I think that there's much traction to the idea of moving from COMPAT_FREEBSDx to some other variable called, for example, COMPAT_FREEBSD_BACK_TO=x, which will give compatibility for binaries as old as FreeBSD x.0, and have all the other magic handled behind the scenes. This would render the inconsistency with COMPAT_FREEBSDx part of the debate completely moot. >>> >>> Doesn't matter. We're still use to COMPAT_FREEBSDx since >>> it's been here so long. So regardless if you rename them >>> to COMPAT_FREEBSD_BACK_TO=x, it is still potentially confusing. >>> >>> COMPAT_ARCH32 and all other choices David mentions seem like >>> much better names - even if there wasn't any existing >>> COMPAT_FREEBSDx knobs. >>> >>> My $0.02. >>> >>> >> >> >> Ill say it again if I have to... COMPAT_ELF32 or possibly even ELF32_SUPPORT >> seems to me as a very likely possibility. >> >> Maybe even: >> SUPPORT_ELF32= # Support for 32 Bit ELF Binaries >> >> This would add its own name structure that is expandabe later-in-future when >> 128 Bit systems come out ;) > > ELF may go away sometime, just like a.out went to the holly pastures. It may. But having a confusing directive (the COMPAT_FREEBSD32 vs COMPAT_FREEBSD[4567]) is likely to stay with us for a long, long, long time. Just like the scarring after a bullet wound to the foot. //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkupYt4ACgkQODUnwSLUlKTWHQCePMfrdHKqTryA5DQ4T8aRlKfM jwUAnRmjdXdAwXB2gEvgNV8609ctqDY9 =q+B1 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2010 13:49, Ian FREISLICH wrote: > Hi > > I originally wasn't going to weigh in on this, but: > > options COMPAT_FREEBSD4 #Compatible with FreeBSD4 > options COMPAT_FREEBSD5 #Compatible with FreeBSD5 > options COMPAT_FREEBSD6 #Compatible with FreeBSD6 > options COMPAT_FREEBSD7 #Compatible with FreeBSD7 > options COMPAT_FREEBSD32 > > Thanks for the advance notice that FreeBSD will be EoL before RELENG_32. > Perhaps "COMPAT_ARCH_32BIT" would've been a smarter move? //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkueMywACgkQODUnwSLUlKS6QgCfTPtf0qlgwuSRTSSjtev5N6zc bG4An2oQhtzEtmaAEzrRs01ClK+nDf/8 =SLia -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Amanda, FreeBSD8, amtype, hairpulling, etc.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.03.2010 15:20, Svein Skogen wrote: > I'm having trouble getting Amanda (2.6.1p2 from ports) to play nicely > with my hardware. > > Devices are: >at scbus0 target 1 lun 0 (sa0,pass0) >at scbus0 target 1 lun 1 (pass1,ch0) > connected via: > mpt0: port 0x9000-0x90ff mem > 0xfe4fc000-0xfe4f,0xfe4e-0xfe4e irq 16 at device 0.0 on pci2 > mpt0: [ITHREAD] > mpt0: MPI Version=1.5.20.0 > > os and number in question is: > FreeBSD storage.stillbilde.net 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Mar > 9 07:01:59 UTC 2010 > sv...@storage.stillbilde.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Tapes are regular LTO-3 (HP C7973A). > > amtapetype simply hangs (after writing 3-4 tps for 5 seconds, then > simple silence both on sa0 and console) > > Has anybody run into this problem with FreeBSD8+mpt+autoloader? > > //Svein > I'm finally starting to make sense of what I'm seeing (hence the crossposting) Seems I've stumbled onto some strange incompatibility between my SAS controller (LSI 3801E), Tape-library, and FreeBSD+Solaris. The behavior I'm seeing is consistent with this solaris bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6894775 but luckily (?) for me, my disks are on an MFI controller. I'm seeing the exact same behavior in both FreeBSD and OpenSolaris 133 and 134. Linux and Windows installs on the box (this box is currently being set up, so I'm rather liberated from reinstall-concerns) seems unaffected, atleast the HP Software doesn't fail the way tar/dump/dd/amanda/bacula/whatnot does at random intervals. The errors only occur when the device I'm reading/writing from is 100% laoded (reading or writing 56mb/sec + compression), which when fed from a raid capable of more than 6 times that is quite likely to happen during backups. The Solaris bug seems to be around MSI handling, but there are several reports "over there" about this error occuring even with MSI disabled. Right now I'm dumbstruck about this, and might install Linux "just to get backups up and running this year", because I'm too tired of this entire process, but I'd REALLY rather run FreeBSD or OpenSolaris. This is based on a personal preference and nothing else, but if anybody has some blinding insights on how to get this working, I'm open for suggestions. //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkubtf8ACgkQODUnwSLUlKTfGgCgndwhQdAjFjlUp2jCh5POr0jp 0rYAoKUsR2AjzlBCM/eqMfUjGfKtWXof =2lnD -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: A tool for remapping bad sectors in CURRENT?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.03.2010 16:21, Dag-Erling Smørgrav wrote: > Miroslav Lachman <000.f...@quip.cz> writes: >> Yes, rewriting by dd or any other way works for reallocating or >> clearing pending sectors counter, but in server environment > > In a server environment, you'd be a fool not to have some sort of > redundancy set up. > >> I need to know the affected file, as it can be for example database >> file and then it is a big problem! Rewriting the sector inside InnoDB >> ib_data file can cause DB crash, data loss etc. > > How is that different from *not* rewriting the sector? If there's a bad > sector somewhere in your data, your database is still going to crash. Only if he hasn't listened to your first advice and set it up on a non-redundant IO solution. If he's set it up on proper hardware, he'll just get a friendly mail about replacing said disk next time he's in the serverroom with a new fresh hostpare. //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuZCyQACgkQODUnwSLUlKS2ngCgqF+bE4SqHC39lYAoMpQG1Ysb IzcAoLusP1O4LV0CDoq3GSXjV3YGDLDk =Ljac -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: propose: all arch move into a separate dir
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.03.2010 11:48, Alex Keda wrote: > On 05.03.2010 12:59, Doug Rabson wrote: >> On 5 Mar 2010, at 09:56, Alex Keda wrote: >> >> >>> On 05.03.2010 12:45, Doug Rabson wrote: >>> On 5 Mar 2010, at 09:30, Alex Keda wrote: > On 05.03.2010 12:17, Robert Watson wrote: > > >> consumers like Isilon, NetApp, Juniper, and many others >> >> > thus, it is not 'Free', this managed by 'consumers like Isilon, > NetApp, Juniper, and many others'? > > It might be helpful to think of them as 'customers' who are using our 'product' and paying for it by feeding back patches and employing FreeBSD developers. Normal business practice doesn't include intentionally making your customers' lives difficult - if you make a habit of it they tend to go elsewhere. >>> It seems to me, business and freedom - are mutually exclusive things. >>> or you can choose the path of development, or who pays - giver >>> commands to community. >>> no freedom there. >>> >> Someone always pays. If this project didn't have sponsors like Isilon, >> NetApp, Juniper, Yahoo, and many others it simply would not exist. >> > > then can a more correct name of the project or ClosedBSD or ManagedBSD? =) > or something abstract? > == > I love FreeBSD, but then having to follow the guidance of someone even > though everyone understands what you can do better - depressing. Oh, so because a lot of the programmers behind it receive wages, and the project itself won't commit ritual suicide by basically blocking the companies using FreeBSD from returning improvements they make to the project itself, it should be renamed. Can I suggest you be careful around bright light sources? //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuQ5IoACgkQODUnwSLUlKTYLACbB37bgcYWrYrFjX0g6StaReSa k+YAn2hLbhcrXzbKoxDNklDhzGcWGEdw =3fZ/ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
