From owner-freebsd-geom@FreeBSD.ORG Mon Mar 20 11:02:43 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A6FF16A400 for ; Mon, 20 Mar 2006 11:02:43 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21FEB43D46 for ; Mon, 20 Mar 2006 11:02:43 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2KB2hqG082479 for ; Mon, 20 Mar 2006 11:02:43 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2KB2faX082468 for freebsd-geom@freebsd.org; Mon, 20 Mar 2006 11:02:41 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Mar 2006 11:02:41 GMT Message-Id: <200603201102.k2KB2faX082468@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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, 20 Mar 2006 11:02:43 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/01/21] kern/76538 geom [gbde] nfs-write on gbde partition stalls o [2005/08/04] kern/84556 geom [geom] GBDE-encrypted swap causes panic a o [2005/10/16] kern/87544 geom [gbde] mmaping large files on a gbde file o [2005/11/16] kern/89102 geom [geom_vfs] [panic] panic when forced unmo o [2005/12/08] bin/90093 geom fdisk(8) incapable of altering in-core ge o [2005/12/18] kern/90582 geom [geom_mirror] [panic] Restore cause panic 6 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/02/26] bin/78131 geom gbde "destroy" not working. o [2005/03/26] kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o [2006/03/18] kern/94632 geom [geom] Kernel output resets input while G 3 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Mar 20 14:23:04 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC41316A41F for ; Mon, 20 Mar 2006 14:23:04 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B330443D5C for ; Mon, 20 Mar 2006 14:23:03 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k2KEN2Qn082849; Mon, 20 Mar 2006 08:23:02 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <441EBAC6.5000406@centtech.com> Date: Mon, 20 Mar 2006 08:23:02 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: "Jeremy C. Reed" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1345/Mon Mar 20 06:03:16 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-geom@freebsd.org Subject: Re: gconcat, growfs followed by fsck and errors 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, 20 Mar 2006 14:23:04 -0000 Jeremy C. Reed wrote: > I don't know if this is geom related. Feel free to point me elsewhere. > > I used gconcat to grow a volume. Then I used growfs. It appeared to be > fine and usable. > > But I read that using fsck is a good idea. But fsck complained: > > fsck: Could not determine filesystem type > > So I used fsck_ufs and it showed many, many errors, such as > UNKNOWN FILE TYPE I=124802 > and many others. > > I now notice that fsck "fsck: Could not determine filesystem type" even > after a newfs of a /dev/label/MYVOLUME. fsck_ufs completed fine. > > After converting new /dev/label/MYVOLUME using: > > glacier# gconcat label MYVOLUME /dev/ad0s2 /dev/md1 > glacier# growfs /dev/concat/MYVOLUME > We strongly recommend you to make a backup before growing the Filesystem > > Did you backup your data (Yes/No) ? Yes > new file systemsize is: 568919 frags > Warning: 138716 sector(s) cannot be allocated. > growfs: 1043.4MB (2136960 sectors) block size 16384, fragment size 2048 > using 14 cylinder groups of 74.53MB, 4770 blks, 9600 inodes. > super-block backups (for fsck -b #) at: > 610720, 763360, 916000, 1068640, 1221280, 1373920, 1526560, 1679200, 1831840, > 1984480 > glacier# fsck /dev/concat/MYVOLUME > fsck: Could not determine filesystem type > glacier# fsck_ufs /dev/concat/MYVOLUME > ** /dev/concat/MYVOLUME > ** Last Mounted on > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > UNREF FILE I=126527 OWNER=1227754098 MODE=62157 > SIZE=0 MTIME=Dec 31 16:00 1969 > RECONNECT? [yn] > > > > CLEAR? [yn] n > > UNREF FILE I=126553 OWNER=538976266 MODE=25453 > SIZE=0 MTIME=Dec 31 16:00 1969 > RECONNECT? [yn] n > > > CLEAR? [yn] n > > UNREF FILE I=127462 OWNER=1327525490 MODE=62562 > SIZE=0 MTIME=Dec 31 16:00 1969 > RECONNECT? [yn] ^C > ***** FILE SYSTEM MARKED DIRTY ***** > > > What can I use to see what these unreferenced files are? > > What is strange is in this example above, I did a newfs and fsck > immediately before using gconcat and growfs. So in other words, these > should be empty filesystems with no inodes. > > By the way, is using /dev/md* as a geom provider a bad idea? > You can use fsdb against the filesystem to get at the information about the inode, amongst other things. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-geom@FreeBSD.ORG Sat Mar 25 13:50:02 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1633516A480 for ; Sat, 25 Mar 2006 13:50:02 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51ABF43D45 for ; Sat, 25 Mar 2006 13:50:01 +0000 (GMT) (envelope-from cochard@gmail.com) Received: by nproxy.gmail.com with SMTP id n28so815709nfc for ; Sat, 25 Mar 2006 05:50:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type; b=qCJ+P9wIzOSckZUKb+ejt+OPfAXXSuvWeNv+i1816xhQgtlGI1zW+P98zCXfG6knx7WM075mOtUQ9s3NUNknsD9eag4nSPBKkDduVoR2J1xYWQsjeJ/8XTyYOnQbttasN2XBe2WzL5pvDf69d3OytZAktL92VN0naZIBVP7mBJA= Received: by 10.48.163.5 with SMTP id l5mr791832nfe; Sat, 25 Mar 2006 05:43:16 -0800 (PST) Received: by 10.48.216.14 with HTTP; Sat, 25 Mar 2006 05:43:16 -0800 (PST) Message-ID: <3131aa530603250543g2b875564s@mail.gmail.com> Date: Sat, 25 Mar 2006 14:43:16 +0100 From: "Olivier Cochard" Sender: cochard@gmail.com To: freebsd-geom@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Gvinum configuration changed after a simple reboot X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Olivier Cochard List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Mar 2006 13:50:02 -0000 Hi all! it's me again torturing gvinum :-) I've found a strange problem with creating gvinum RAID 5 volume. I can reproduce this problem at each time. I'm working with a VMware workstation PC with a 6.1-PRERELEASE and 3 hard drive: - ad0: 102Mb - ad1: 204mb - ad3: 306mb And I want to test a RAID 5 volume with these 3 disks. Then I create this config file: $ cat /var/etc/raid.conf drive disk_ad0 device /dev/ad0s1a drive disk_ad1 device /dev/ad1s1a drive disk_ad3 device /dev/ad3s1a volume raid plex org raid5 256k sd length 0 drive disk_ad0 sd length 0 drive disk_ad1 sd length 0 drive disk_ad3 With this configuration I should obtain a 204Mb RAID5 volume (2 * 102Mb). And gvinum confirm that's right with this output: Software RAID information and status: 3 drives: D disk_ad3 State: up /dev/ad3s1a A: 0/306 MB (0%) D disk_ad1 State: up /dev/ad1s1a A: 0/204 MB (0%) D disk_ad0 State: up /dev/ad0s1a A: 0/102 MB (0%) 1 volume: V raid State: up Plexes: 1 Size: 204 MB 1 plex: P raid.p0 R5 State: up Subdisks: 3 Size: 204 MB 3 subdisks: S raid.p0.s2 State: up D: disk_ad3 Size: 306 MB S raid.p0.s1 State: up D: disk_ad1 Size: 204 MB S raid.p0.s0 State: up D: disk_ad0 Size: 102 MB I can launch a newfs on it without problem, and put file on it ... All seem ok. But... when I reboot the VMWare workstation.. I obtain this: Software RAID status: 3 drives: D disk_ad0 State: up /dev/ad0s1a A: 0/102 MB (0%) D disk_ad1 State: up /dev/ad1s1a A: 0/204 MB (0%) D disk_ad3 State: up /dev/ad3s1a A: 0/306 MB (0%) 1 volume: V raid State: up Plexes: 1 Size: 613 MB 1 plex: P raid.p0 R5 State: up Subdisks: 3 Size: 613 MB 3 subdisks: S raid.p0.s0 State: up D: disk_ad0 Size: 102 MB S raid.p0.s1 State: up D: disk_ad1 Size: 204 MB S raid.p0.s2 State: up D: disk_ad3 Size: 306 MB The total RAID volume space change... and I can't use it anymore!! (must be delete). $ fsck -t ufs /dev/gvinum/raid Cannot find file system superblock fsck_ufs: /dev/gvinum/raid: can't read disk label ** /dev/gvinum/raid ioctl (GCINFO): Inappropriate ioctl for device Any idea ? Thanks, Olivier -- Olivier Cochard FreeNAS main developer http://www.freenas.org Skype: callto://ocochard From owner-freebsd-geom@FreeBSD.ORG Sat Mar 25 14:40:43 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C2616A429 for ; Sat, 25 Mar 2006 14:40:43 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAF3843D68 for ; Sat, 25 Mar 2006 14:40:38 +0000 (GMT) (envelope-from cochard@gmail.com) Received: by nproxy.gmail.com with SMTP id q29so624332nfc for ; Sat, 25 Mar 2006 06:40:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:references; b=reFEvCzn447Ha34Bn6j6a9pC58IpjDl0NRsZIUb2k2ZkXZo6FPI+P+MigtHnAVI9wDZ3igM6zv3CtTk2GR2gxAnCsGXx/RO95EAVIn0bSlM+BQ6mwSy8rjFqVo9oNCTKZWjohFEqe8zRQ/HmOZm/i+jgzkiShT9jV6yikzias2Q= Received: by 10.48.163.5 with SMTP id l5mr802971nfe; Sat, 25 Mar 2006 06:14:17 -0800 (PST) Received: by 10.48.216.14 with HTTP; Sat, 25 Mar 2006 06:14:16 -0800 (PST) Message-ID: <3131aa530603250614m7d815306l@mail.gmail.com> Date: Sat, 25 Mar 2006 15:14:16 +0100 From: "Olivier Cochard" Sender: cochard@gmail.com To: freebsd-geom@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <3131aa530603111021x183cdb67y@mail.gmail.com> <3131aa530603141459ge9bf401u@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: gvinum: problem for adding drives X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Olivier Cochard List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Mar 2006 14:40:43 -0000 I try to use the 'sd length 0' for mirroring 2 disks of different size. - ad0 is a 102Mb hard drive - ad1 is a 204Mb hard drive Then I use "concat" for obtain mirroring (chapter 19.6.2 "Increased Resilience: Mirroring" of the FreeBSD handbook). Here is the config file: $ cat /var/etc/raid.conf drive disk_ad0 device /dev/ad0s1a drive disk_ad1 device /dev/ad1s1a volume titi plex org concat sd length 0 drive disk_ad0 plex org concat sd length 0 drive disk_ad1 Normally, I should have one volume of 102Mb... But gvinum create a volume of 204Mb... Software RAID information and status: 2 drives: D disk_ad1 State: up /dev/ad1s1a A: 0/204 MB (0%) D disk_ad0 State: up /dev/ad0s1a A: 0/102 MB (0%) 1 volume: V titi State: up Plexes: 2 Size: 204 MB 2 plexes: P titi.p1 C State: up Subdisks: 1 Size: 204 MB P titi.p0 C State: up Subdisks: 1 Size: 102 MB 2 subdisks: S titi.p1.s0 State: up D: disk_ad1 Size: 204 MB S titi.p0.s0 State: up D: disk_ad0 Size: 102 MB Then here are my question: - Is 'concat' equivalent to mirroring ? - Can I use a 'sd lenght 0' for disk with different size for 'concat' ? Thanks, Olivier 2006/3/15, Lukas Ertl : > > On Tue, 14 Mar 2006, Olivier Cochard wrote: > > > Is the 'sd length 0 drive' works for all RAID type ? > > Yes. > > regards, > le > > -- > Lukas Ertl http://homepage.univie.ac.at/l.ertl/ > le@FreeBSD.org http://people.freebsd.org/~le/ >