similar to: bugged sysinstall, bsdlabel, zfs, gmirror - recept for disaster :)

Displaying 20 results from an estimated 400 matches similar to: "bugged sysinstall, bsdlabel, zfs, gmirror - recept for disaster :)"

2012 Mar 28
2
problem: bsdlabel
hail, I partitioned the disk this way: fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size
2006 Mar 06
6
gmirror(8) and graid3(8) changes.
Hi. Here you can find patches with changes to gmirror(8) and graid3(8): http://people.freebsd.org/~pjd/patches/gmirror.7.patch http://people.freebsd.org/~pjd/patches/graid3.patch The patches does the following: - Significant synchronization speed improvement. Now many parallel synchronization I/O requests can be used instead of only one before. Many people requested this. - Close race
2013 Nov 28
2
gmirror: writes are faster than reads
Hi Guys, Has somebody encountered (significantly) different read/write speeds when using gmirror? I have 2xWD WD30EFRX RED drives which are configured as follows: $ gmirror status Name Status Components mirror/root COMPLETE ada0p2 (ACTIVE) ada1p2 (ACTIVE) mirror/data COMPLETE ada0p4 (ACTIVE) ada1p4 (ACTIVE) mirror/root is mounted
2008 Nov 19
2
gmirror and gstripe
hail, I have an old AthlonXP 1700+ running 7-STABLE: FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13 23:54:59 BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386 where I have two 750GB Seagate SATA Disks. They are divided as two slices, around the first 120GB are gathered in gmirror, and what left is in gstripe. so that's whats going on. if the machine locks, and fsck comes to
2007 Apr 04
1
sun x2100 gmirror problem
Hi, We're using gmirror on our sun fire x2100 and FreeBSD 6.1-p10. Some days ago I found this in the logs: Apr 1 02:12:05 x2100 kernel: ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=612960533 Apr 1 02:12:05 x2100 kernel: ad6: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=612960533 Apr 1 02:12:05 x2100 kernel: GEOM_MIRROR:
2006 Mar 15
2
swap at beginning of slice - danger?
Hello freebsd-stable, I have 5.5-PRERELEASE server in production, booting from ad0s1: # BLOCKSIZE=512 swapinfo Device 512-blocks Used Avail Capacity /dev/ad0s1b 2097152 52872 2044280 3% /dev/ad1s1b 2097152 51952 2045200 2% Total 4194304 104824 4089480 2% # bsdlabel ad0s1 | fgrep b: b: 2097152 0 swap
2013 Aug 29
2
gmirror crash writing to disk? Or is it su+j crash?
So I have a system running: FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55 EDT 2013 root at walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386 and it has two 2T SATA disks. To keep this post short, the crash.txt is here. https://uk.eicat.ca/owncloud/public.php?service=files&t=fea9d25579fe0c4afb808859e80e1493 now curiously, while running a "make -j4
2012 Feb 11
3
9.0-RELEASE PV from scratch on XCP v1.1.0
Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under
2008 Jun 26
1
gmirror+gjournal: unable to boot after crash
Hi, after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. This is what I get with kernel.geom.mirror.debug=2: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB <SAMSUNG HD501LJ
2008 Aug 20
1
boot0cfg and gmirror ...
Hi, all, I know about the "foot shooting" prevention in geom(4) when trying to update the MBR of a mounted disk. I have a system with ad4 and ad6 mirrored and fdisk partitions residing on the mirror to be booted alterningly: hd30# gmirror status Name Status Components mirror/m0 COMPLETE ad4 ad6 hd30# mount /dev/mirror/m0s1a on / (ufs, local, read-only)
2008 Jul 09
2
disk questions: geom and zfs
hail, I have a 7-stable: [matheus@xxx /usr/home/matheus]$ uname -a FreeBSD xxx 7.0-STABLE FreeBSD 7.0-STABLE #2: Sun Jul 6 15:03:26 BRT 2008 root@lamneth:/usr/obj/usr/src/sys/xxx_7 i386 and there exists three geom things. gconcat status Name Status Components concat/concat0 UP ad4 ad5 gmirror status Name Status Components
2008 Jul 22
1
unable to use gmirror on supermicro 5015b-mt
These are new boxes. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm core 2 Q6600 CPU 8Gb 667 RAM Boxes were memtested from Fri-Mon okay. 6.3-RELEASE (amd64) installs fine. Build cycle okay. Running (no load) for a week or so. However, when I try to configure gmirror they hang on boot. After some fiddling it appears issuing #kldload geom_mirror hangs the boxes very hard.
2008 Jul 15
5
Multi-machine mirroring choices
With the introduction of zfs to FreeBSD 7.0, a door has opened for more mirroring options so I would like to get some opinions on what direction I should take for the following scenario. Basically I have 2 machines that are "clones" of each other (master and slave) wherein one will be serving up samba shares. Each server has one disk to hold the OS (not mirrored) and then 3 disks, each
2013 Jun 19
3
shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount
Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers
2003 Sep 04
1
ext2fs BSD-slice subpartition?
Hi everyone, I extracted this from the grub sourcecode: /* possible values for the *BSD-style partition type */ . . . #define FS_EXT2FS 17 /* Linux Extended 2 file system */ It would actually meet my partitioning requirements to register a partition inside one of my slices as ext2 (I currently mask the partition type as ISO9660(!) and use a *patched* grub, so you see this situation
2011 Mar 07
1
Initialising UPS variables from ups.conf
Are there any plans to allow us to specify UPS variables in ups.conf, eg: [evo_s_3000] driver = usbhid-ups port = auto desc = "Eaton Evolution S 3000" vendorid = 0463 productid = ffff ups.delay.shutdown = 120 ups.delay.start = 130 The reason I ask is that I'm using FreeBSD & gmirror and need to extend the gracetime
2006 Mar 15
0
fdisk, sysinstall and 6.1-BETA3/amd64
Hi folks, I'm moving a server over to amd64 in the next week or so and I'm preparing the RAID1 disk set with the 64 bit ports as we speak. I came across a nasty little bug whilst doing so. Motherboard is a Gigabyte GA-K8U with a ULi SATA controller and AR0 set up as a RAID1 array using FreeBSD pseudo-RAID (ULi's metadata isn't supported). So far, so good. Then into sysinstall
2003 May 13
0
Updating sysinstall
Hi list, After a few updates from 4.4 through 4.8 using csvup, I want to update /stand/sysinstall et al in case of emergency. cd /usr/src/release/sysinstall && make all install works as expected, but only updates the stand binary. Allthough it's only a single binary, how do I build and install boot_crunch to /stand without building and figuring out a complete release-build? And, as
2008 Jan 20
2
Dell Perc 6 disk geometry problem with RAID5 (both 6.3 final and 7.0 RC1)
Hi, We bought a new Dell PowerEdge 2950III with Perc 6/i and have the disk geometry problem using 6.3 final or 7.0 RC1. Seems that we are not alone at least one guy has similar problem reported earlier: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg00506.html I was reading the mailing list and found that some of the people are happily using this hardware with the latest
2008 May 26
2
Why does sysinstall still limits cylinders to 65535?
Hello, I have been struglling with sysinstall, attempting to make it handle the geometry of some large SATA drives. After a lot of effort I decided to stop suffering and modified the program in order to circumvent the outdated limit of 65535 cylinders (see attached patch). I'm thinking about submitting a PR with a change request but I'd like to get some additional opinions first. I did