From owner-freebsd-geom@FreeBSD.ORG Sun Jul 13 00:58:23 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E24E6106564A for ; Sun, 13 Jul 2008 00:58:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B50EF8FC0C for ; Sun, 13 Jul 2008 00:58:22 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4879532F.7000603@FreeBSD.org> Date: Sun, 13 Jul 2008 02:58:23 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: freebsd-geom@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: GEOM_STRIPE device wackiness X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2008 00:58:24 -0000 I tried to create a stripe on two disks, after writing a new label to overwrite the previous one (all filesystems and swap had been unconfigured). No slices were in use on the disk and I did gstripe label -v -s 131072 data /dev/da0d /dev/da1d newfs worked fine, etc. Rebooted, and geom decided my da0 needed to sprout a da0s1, and that the gstripe should attach there (actually the da0? devices were completely gone). The filesystem was corrupt because the offsets were now all wrong on one of the disks. Rebooting into single-user mode the devices were sort of back: # ls -l /dev/da0* crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d crw-r----- 1 root operator 0, 78 Jul 13 00:48 /dev/da0d crw-r----- 1 root operator 0, 79 Jul 13 00:48 /dev/da0s1 crw-r----- 1 root operator 0, 84 Jul 13 00:48 /dev/da0s1b crw-r----- 1 root operator 0, 85 Jul 13 00:48 /dev/da0s1c crw-r----- 1 root operator 0, 86 Jul 13 00:48 /dev/da0s1d "da0cs1"? Uh ok. # bsdlabel -r /dev/da0 # /dev/da0: 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 33554432 16 swap c: 143638992 0 unused 0 0 # "raw" part, don't edit d: 110084544 33554448 4.2BSD 0 0 0 ...still looks fine # gstripe destroy data GEOM_STRIPE: Disk da0d removed from data. GEOM_STRIPE: Device data destroyed. # gstripe label -v -s 131072 -h data /dev/da0d /dev/da1d GEOM_STRIPE: Device data created (id=2560258567). GEOM_STRIPE: Disk da0s1d attached to data. GEOM_STRIPE: Disk da0s1d removed from data. GEOM_STRIPE: Device data destroyed. GEOM_STRIPE: Device data created (id=476052638). GEOM_STRIPE: Disk da0d attached to data. GEOM_STRIPE: Device data already configured. GEOM_STRIPE: Cannot create device data. Metadata value stored on da0d. GEOM_STRIPE: Disk da1d attached to data. GEOM_STRIPE: Device data activated. Metadata value stored on da1d. Done. Why all this craziness? Now I can mount the filesystem again, but still: # ls -l /dev/da0* crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d crw-r----- 1 root operator 0, 78 Jul 13 00:49 /dev/da0d What's going on here? Kris From owner-freebsd-geom@FreeBSD.ORG Mon Jul 14 11:06:58 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94E701065677 for ; Mon, 14 Jul 2008 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 893368FC2E for ; Mon, 14 Jul 2008 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6EB6wmp014417 for ; Mon, 14 Jul 2008 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6EB6vSD014413 for freebsd-geom@FreeBSD.org; Mon, 14 Jul 2008 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Jul 2008 11:06:57 GMT Message-Id: <200807141106.m6EB6vSD014413@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2008 11:06:58 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/123962 geom [panic] gjournal(8): gjournal (455Gb data, 8Gb journal o kern/124130 geom [gmirror][usb] gmirror fails to start usb devices that o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s 22 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde(8) "destroy" not working. o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile f kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con 15 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Jul 14 19:05:08 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F11581065676 for ; Mon, 14 Jul 2008 19:05:08 +0000 (UTC) (envelope-from tapan.list@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0458FC23 for ; Mon, 14 Jul 2008 19:05:08 +0000 (UTC) (envelope-from tapan.list@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so1891065mue.3 for ; Mon, 14 Jul 2008 12:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=AJGygZ1yc9bVj2N5sDZ6l8wLoY4Vy7uTexns4xgPwr0=; b=RnquVgg/OuMITjczQlqNuTbJcZsUwy/Gf+Tm1HNU86R9BG5W+S25NUCCsLelVsjLTI 7wvurtS3ycz76zp/aDm3Eea4RXc6O/HovEBs3SBN7HxnM2vWN8QajX+1gJvZAGnlgVCa DGSn6uEfkNNmhpT2FM02xIJ95At9RqAYSlFZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=P7jmgJd9U+c1eRuM2BWk2toMHMK4NTFTwwSVVHOeVNjs47gLXVydJrgvy9k0mICnjd arikwtealaAZ//ED6LuRaB5uHQHmX692paPa9CevkVSnBSF+/G5TmjFkFfA3bmezhdJd 2k8QmdDcTakc7JfLVGIg0wzEmv5OkYyFI7G1o= Received: by 10.103.213.10 with SMTP id p10mr8184982muq.46.1216062306849; Mon, 14 Jul 2008 12:05:06 -0700 (PDT) Received: by 10.103.227.19 with HTTP; Mon, 14 Jul 2008 12:05:06 -0700 (PDT) Message-ID: <482257ad0807141205i1d5e2c2co4b609a9f5b7015b@mail.gmail.com> Date: Tue, 15 Jul 2008 00:35:06 +0530 From: "Tapan Chaudhari" To: freebsd-geom@freebsd.org In-Reply-To: <482257ad0807111209g20cdb0f6j9f7000fd57a7287a@mail.gmail.com> MIME-Version: 1.0 References: <482257ad0807100541s2d2c3d1eo6cd57c3a1bc338d1@mail.gmail.com> <200807102309.03191.mark@legios.org> <482257ad0807100655u1a5c660awfad05564e40e9a95@mail.gmail.com> <482257ad0807111129i66ac4372sbc9b4d4ef7675e9d@mail.gmail.com> <482257ad0807111209g20cdb0f6j9f7000fd57a7287a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Can GEOM be used to intercept the I/o calls to an existing mounted device? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2008 19:05:09 -0000 Hi All, I am not able to find ways to intercept the i/o calls. I will need your help to move ahead. One thing to mention is 'mirror' is just an example. I want to write a new driver which will intercept the i/o calls. This is the first major milestone to achieve. Needed your help. Any pointers and directions will do. Thanks, --Tapan. On Sat, Jul 12, 2008 at 12:39 AM, Tapan Chaudhari wrote: > Hi, > I got the problem resolved of not getting mails. It was the stupid of me > that changed the settings :-).. I have unchecked the digest. > > Did Ivan sent some attachment with the mail? An attachment was scrubbed in > the digest I received. Sorry for the trouble but still, can anyone resend > it? > Expecting some help regarding "interception mechanism" from all of you. > > > Thanks, > --Tapan. > > > On Fri, Jul 11, 2008 at 11:59 PM, Tapan Chaudhari > wrote: > >> Hey guys, >> First of all, I was not able to receive your replies to my mail. I >> don't know the reason but I am already subscribed to the list. I got to know >> about your replies from the digest i received today. I have written a mail >> to the mailing list owner describing this problem. Hope this does not happen >> again. >> >> >> Well regarding GEOM as Poul mentioned he has already done this >> interception mechanism in GEOM, Poul can you please help me out by giving >> some directions as to how to move ahead and implement the interceptions of >> i/o to a particular device? I would be really happy to get any help >> regarding the interception mechanism. >> >> Thanks, >> --Tapan. >> >> >> On Thu, Jul 10, 2008 at 7:25 PM, Tapan Chaudhari >> wrote: >> >>> Thanks Mark, but unmounting will anyways work. But the problem here will >>> be, a new device "/dev/mirror/gm0" and "/dev/mirror/gm0s1" will be created >>> after :- >>> >>> #gmirror label -v -n -b round-robin gm0 /dev/md0 >>> #gmirror load >>> #gmirror configure -a gm0 >>> >>> and "/dev/md0s1" gets deleted. >>> Now I will have to mount the new device "/dev/mirror/gm0s1" to get my >>> original contents. >>> Can't I do it on the fly while the device is already mounted? I just want >>> that all the calls going to the device "/dev/md0s1" first come to me and >>> then it goes to the original device. In short intercepting the i/o calls. Is >>> there some way I can achieve this? >>> >>> Thanks, >>> >>> >>> On Thu, Jul 10, 2008 at 6:39 PM, Mark Gladman wrote: >>> >>>> On Thursday 10 July 2008 22:41:25 Tapan Chaudhari wrote: >>>> > Hi All, >>>> > I am a newbie to FreeBSD and GEOM. I wanted to intercept the i/o >>>> calls >>>> > going to a particular mounted device by writing some driver. >>>> > I came across geom and thought it might work. I tried to create a new >>>> > device, mount it and then tried using gmirror to mirror the device :- >>>> > >>>> > #dd if=/dev/zero of=file1 bs=1M count=10 >>>> > #dd if=/dev/zero of=file2 bs=1M count=10 >>>> > #mdconfig -f file1 >>>> > #mdconfig -f file2 >>>> > #fdisk -B /dev/mirror/md0 >>>> > #newfs /dev/mirror/md0s1 >>>> > #mkdir /mnt/mirror0 >>>> > #mount /dev/mirror/md0s1 /mnt/mirror0/ >>>> > >>>> > #gmirror label -v -n -b round-robin gm0 /dev/md0 >>>> > gmirror: Can't store metadata on /dev/md0: Operation not permitted. >>>> > >>>> > It gave me this error "gmirror: Can't store metadata on /dev/md0: >>>> Operation >>>> > not permitted." >>>> > >>>> > Am I doing something wrong? Or GEOM does not permit me intercept the >>>> i/o >>>> > calls? If not geom, is there any other mechanism by which I can >>>> achieve it? >>>> > >>>> > >>>> > Thanks, >>>> > --Tapan. >>>> > _______________________________________________ >>>> > freebsd-geom@freebsd.org mailing list >>>> > http://lists.freebsd.org/mailman/listinfo/freebsd-geom >>>> > To unsubscribe, send any mail to " >>>> freebsd-geom-unsubscribe@freebsd.org" >>>> >>>> Hey, >>>> >>>> You're attempting to set up gmirror on a mounted device. >>>> Unmount /dev/mirror/md0s1 then retry the gmirror command and it should >>>> work. >>>> >>>> Cheers! >>>> Mark >>>> >>> >>> >> > From owner-freebsd-geom@FreeBSD.ORG Tue Jul 15 17:08:40 2008 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF1FA106566C; Tue, 15 Jul 2008 17:08:40 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 86BAB8FC1B; Tue, 15 Jul 2008 17:08:40 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6FH8eZa009494; Tue, 15 Jul 2008 17:08:40 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6FH8eJm009490; Tue, 15 Jul 2008 17:08:40 GMT (envelope-from gavin) Date: Tue, 15 Jul 2008 17:08:40 GMT Message-Id: <200807151708.m6FH8eJm009490@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-geom@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/125632: [gvinum] rename does not work for drive objects X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 17:08:40 -0000 Old Synopsis: gvinum rename does not work for drive objects New Synopsis: [gvinum] rename does not work for drive objects Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: gavin Responsible-Changed-When: Tue Jul 15 17:08:04 UTC 2008 Responsible-Changed-Why: Over to maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=125632 From owner-freebsd-geom@FreeBSD.ORG Tue Jul 15 21:01:52 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF910106566B; Tue, 15 Jul 2008 21:01:52 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 21BA68FC15; Tue, 15 Jul 2008 21:01:50 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <487D1041.70702@FreeBSD.org> Date: Tue, 15 Jul 2008 23:01:53 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <4879532F.7000603@FreeBSD.org> In-Reply-To: <4879532F.7000603@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@FreeBSD.org Subject: Re: GEOM_STRIPE device wackiness X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 21:01:52 -0000 Kris Kennaway wrote: > I tried to create a stripe on two disks, after writing a new label to > overwrite the previous one (all filesystems and swap had been > unconfigured). No slices were in use on the disk and I did > > gstripe label -v -s 131072 data /dev/da0d /dev/da1d > > newfs worked fine, etc. Rebooted, and geom decided my da0 needed to > sprout a da0s1, and that the gstripe should attach there (actually the > da0? devices were completely gone). The filesystem was corrupt because > the offsets were now all wrong on one of the disks. > > Rebooting into single-user mode the devices were sort of back: > > # ls -l /dev/da0* > crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 > crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b > crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c > crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 > crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b > crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c > crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d > crw-r----- 1 root operator 0, 78 Jul 13 00:48 /dev/da0d > crw-r----- 1 root operator 0, 79 Jul 13 00:48 /dev/da0s1 > crw-r----- 1 root operator 0, 84 Jul 13 00:48 /dev/da0s1b > crw-r----- 1 root operator 0, 85 Jul 13 00:48 /dev/da0s1c > crw-r----- 1 root operator 0, 86 Jul 13 00:48 /dev/da0s1d > > "da0cs1"? Uh ok. > > # bsdlabel -r /dev/da0 > # /dev/da0: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > b: 33554432 16 swap > c: 143638992 0 unused 0 0 # "raw" part, > don't edit > d: 110084544 33554448 4.2BSD 0 0 0 > > ...still looks fine > > # gstripe destroy data > GEOM_STRIPE: Disk da0d removed from data. > GEOM_STRIPE: Device data destroyed. > # gstripe label -v -s 131072 -h data /dev/da0d /dev/da1d > GEOM_STRIPE: Device data created (id=2560258567). > GEOM_STRIPE: Disk da0s1d attached to data. > GEOM_STRIPE: Disk da0s1d removed from data. > GEOM_STRIPE: Device data destroyed. > GEOM_STRIPE: Device data created (id=476052638). > GEOM_STRIPE: Disk da0d attached to data. > GEOM_STRIPE: Device data already configured. > GEOM_STRIPE: Cannot create device data. > Metadata value stored on da0d. > GEOM_STRIPE: Disk da1d attached to data. > GEOM_STRIPE: Device data activated. > Metadata value stored on da1d. > Done. > > Why all this craziness? > > Now I can mount the filesystem again, but still: > > # ls -l /dev/da0* > crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 > crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b > crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c > crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 > crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b > crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c > crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d > crw-r----- 1 root operator 0, 78 Jul 13 00:49 /dev/da0d > > What's going on here? > > Kris > More wackiness: > # gstripe destroy disk > GEOM_STRIPE: Disk da0d removed from disk. > GEOM_STRIPE: Device disk removed. > GEOM_STRIPE: Disk da1d removed from disk. > GEOM_STRIPE: Device disk destroyed. > # gstripe clear da0 > Can't clear metadata on da0: Operation not permitted. > gstripe: Not fully done. > # swapoff /dev/da0b > # gstripe clear da0 > GEOM_STRIPE: Device disk created (id=4082191315). > GEOM_STRIPE: Disk da0d attached to disk. > Can't clear metadata on da0: Invalid argument. > gstripe: Not fully done. (whee my stripe is back) > # dd if=/dev/zero of=/dev/da0 bs=1m count=16 > GEOM_STRIPE: Disk da0d removed from disk. > GEOM_STRIPE: Device disk removed. > 16+0 records in > 16+0 records out > 16777216 bytes transferred in 1.307623 secs (12830317 bytes/sec) Kris From owner-freebsd-geom@FreeBSD.ORG Wed Jul 16 06:02:33 2008 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC61E106564A; Wed, 16 Jul 2008 06:02:33 +0000 (UTC) (envelope-from lulf@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 88C318FC12; Wed, 16 Jul 2008 06:02:33 +0000 (UTC) (envelope-from lulf@FreeBSD.org) Received: from freefall.freebsd.org (lulf@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6G62XY8080761; Wed, 16 Jul 2008 06:02:33 GMT (envelope-from lulf@freefall.freebsd.org) Received: (from lulf@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6G62XMi080757; Wed, 16 Jul 2008 06:02:33 GMT (envelope-from lulf) Date: Wed, 16 Jul 2008 06:02:33 GMT Message-Id: <200807160602.m6G62XMi080757@freefall.freebsd.org> To: lulf@FreeBSD.org, freebsd-geom@FreeBSD.org, lulf@FreeBSD.org From: lulf@FreeBSD.org Cc: Subject: Re: kern/125632: [gvinum] rename does not work for drive objects X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 06:02:33 -0000 Synopsis: [gvinum] rename does not work for drive objects Responsible-Changed-From-To: freebsd-geom->lulf Responsible-Changed-By: lulf Responsible-Changed-When: Wed Jul 16 06:01:41 UTC 2008 Responsible-Changed-Why: - I'll look at this later today. http://www.freebsd.org/cgi/query-pr.cgi?pr=125632 From owner-freebsd-geom@FreeBSD.ORG Fri Jul 18 09:50:21 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 434A41065676 for ; Fri, 18 Jul 2008 09:50:21 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045140.chello.pl [87.206.45.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3FB2A8FC1D for ; Fri, 18 Jul 2008 09:50:20 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id AE4FE45C99; Mon, 14 Jul 2008 08:41:25 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9C9C7456AB; Mon, 14 Jul 2008 08:41:19 +0200 (CEST) Date: Mon, 14 Jul 2008 08:41:20 +0200 From: Pawel Jakub Dawidek To: Kris Kennaway Message-ID: <20080714064120.GA13560@garage.freebsd.pl> References: <4879532F.7000603@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline In-Reply-To: <4879532F.7000603@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@FreeBSD.org Subject: Re: GEOM_STRIPE device wackiness X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2008 09:50:21 -0000 --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 13, 2008 at 02:58:23AM +0200, Kris Kennaway wrote: > I tried to create a stripe on two disks, after writing a new label to=20 > overwrite the previous one (all filesystems and swap had been=20 > unconfigured). No slices were in use on the disk and I did >=20 > gstripe label -v -s 131072 data /dev/da0d /dev/da1d >=20 > newfs worked fine, etc. Rebooted, and geom decided my da0 needed to=20 > sprout a da0s1, and that the gstripe should attach there (actually the=20 > da0? devices were completely gone). The filesystem was corrupt because= =20 > the offsets were now all wrong on one of the disks. >=20 > Rebooting into single-user mode the devices were sort of back: >=20 > # ls -l /dev/da0* > crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 > crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b > crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c > crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 > crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b > crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c > crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d > crw-r----- 1 root operator 0, 78 Jul 13 00:48 /dev/da0d > crw-r----- 1 root operator 0, 79 Jul 13 00:48 /dev/da0s1 > crw-r----- 1 root operator 0, 84 Jul 13 00:48 /dev/da0s1b > crw-r----- 1 root operator 0, 85 Jul 13 00:48 /dev/da0s1c > crw-r----- 1 root operator 0, 86 Jul 13 00:48 /dev/da0s1d >=20 > "da0cs1"? Uh ok. >=20 > # bsdlabel -r /dev/da0 > # /dev/da0: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > b: 33554432 16 swap > c: 143638992 0 unused 0 0 # "raw" part,=20 > don't edit > d: 110084544 33554448 4.2BSD 0 0 0 >=20 > ...still looks fine >=20 > # gstripe destroy data > GEOM_STRIPE: Disk da0d removed from data. > GEOM_STRIPE: Device data destroyed. > # gstripe label -v -s 131072 -h data /dev/da0d /dev/da1d > GEOM_STRIPE: Device data created (id=3D2560258567). > GEOM_STRIPE: Disk da0s1d attached to data. > GEOM_STRIPE: Disk da0s1d removed from data. > GEOM_STRIPE: Device data destroyed. > GEOM_STRIPE: Device data created (id=3D476052638). > GEOM_STRIPE: Disk da0d attached to data. > GEOM_STRIPE: Device data already configured. > GEOM_STRIPE: Cannot create device data. > Metadata value stored on da0d. > GEOM_STRIPE: Disk da1d attached to data. > GEOM_STRIPE: Device data activated. > Metadata value stored on da1d. > Done. >=20 > Why all this craziness? >=20 > Now I can mount the filesystem again, but still: >=20 > # ls -l /dev/da0* > crw-r----- 1 root operator 0, 74 Jul 13 00:48 /dev/da0 > crw-r----- 1 root operator 0, 76 Jul 13 00:48 /dev/da0b > crw-r----- 1 root operator 0, 77 Jul 13 00:48 /dev/da0c > crw-r----- 1 root operator 0, 83 Jul 13 00:48 /dev/da0cs1 > crw-r----- 1 root operator 0, 87 Jul 13 00:48 /dev/da0cs1b > crw-r----- 1 root operator 0, 88 Jul 13 00:48 /dev/da0cs1c > crw-r----- 1 root operator 0, 89 Jul 13 00:48 /dev/da0cs1d > crw-r----- 1 root operator 0, 78 Jul 13 00:49 /dev/da0d >=20 > What's going on here? Most likely trash BSD label metadata. Try doing: # dd if=3D/dev/zero of=3D/dev/da0 count=3D79 first and then bsdlabel and gstripe it again. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFIevUQForvXbEpPzQRAoV0AJ0V/sTvGKKjFCR0froov03LQZvaUACgsUnq KPJh2KY/Zon6+amKJ/O+n2Q= =P4bP -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X--