From owner-freebsd-fs@FreeBSD.ORG Mon Nov 29 06:58:50 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 623AA16A4CE
for <freebsd-fs@freebsd.org>; Mon, 29 Nov 2004 06:58:50 +0000 (GMT)
Received: from web50709.mail.yahoo.com (web50709.mail.yahoo.com
[206.190.38.250])
by mx1.FreeBSD.org (Postfix) with SMTP id E969543D41
for <freebsd-fs@freebsd.org>; Mon, 29 Nov 2004 06:58:49 +0000 (GMT)
(envelope-from weyrich_comp@yahoo.com)
Received: (qmail 40087 invoked by uid 60001); 29 Nov 2004 06:58:49 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
b=Kr82meGZh2VQq0IZw2XQLqZ7Iu0+JKPGwwmHJZacyCQAYpjPzOcg9Agz2AcbzdK+uZAbPYSDPiiDh4d+B0OzBMN6WyZQF8kLMdKHjsMpijhi58YM+QU1KZw++Txu1nZlxCkZy9CS4mEIVDBYyaX4WfuN5jzXEeXtzRkbZ8GlQr4=
;
Message-ID: <20041129065849.40085.qmail@web50709.mail.yahoo.com>
Received: from [64.249.12.251] by web50709.mail.yahoo.com via HTTP;
Sun, 28 Nov 2004 22:58:49 PST
Date: Sun, 28 Nov 2004 22:58:49 -0800 (PST)
From: orville weyrich <weyrich_comp@yahoo.com>
To: freebsd-fs@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: FDISK Woes
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2004 06:58:50 -0000
I did a stupid thing and zapped my system disk
(/dev/ad0) with FDISK and Label (in
/stand/sysinstall)instead of /dev/da0. Needless to
say, my system is sick.
Is there a way to mount this zapped system disk into
another system and reconstruct the disk label? (I
need to find the locations of the / (ad0s1a), /usr
(ad0s1f), and /var (ad0s1e), and then write a suitable
disk label without destroying the data on the disk.
I feel so dumb doing this, but it seems strange that
would allow me to zap the label of a mounted disk.
Anyway, please help me save my system!
TIA
orvile.
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
From owner-freebsd-fs@FreeBSD.ORG Mon Nov 29 19:00:45 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 17CB416A4D4
for <freebsd-fs@freebsd.org>; Mon, 29 Nov 2004 19:00:21 +0000 (GMT)
Received: from mail.squidge.com (mail0.squidge.com [195.10.252.14])
by mx1.FreeBSD.org (Postfix) with ESMTP id 1730643D5F
for <freebsd-fs@freebsd.org>; Mon, 29 Nov 2004 19:00:21 +0000 (GMT)
(envelope-from henry@jot.to)
Received: from lightbox (82-70-14-145.dsl.in-addr.zen.co.uk [82.70.14.145])
(authenticated bits=0)
by mail.squidge.com (8.12.11/8.12.9) with ESMTP id iATJ0Frq039658
for <freebsd-fs@freebsd.org>; Mon, 29 Nov 2004 19:00:15 GMT
Message-ID: <000b01c4d645$c0ff97c0$0a64a8c0@techiebod.com>
From: "Henry Whincup" <henry@jot.to>
To: <freebsd-fs@freebsd.org>
Date: Mon, 29 Nov 2004 19:00:53 -0000
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by AMaViS at mail.squidge.com
X-Spam-Level: 0.0
Subject: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2004 19:00:45 -0000
On a machine with a 5TB array I created a single partition via gpt and a
filesystem using the defaults from newfs.
All seemed well until I tried to fill the partition with data. With "only"
870GB or so used utilities started reporting the disk as full. Shortly (a
few hours) after the machine panic'd.
During this time I had been trying to copy file via nfs and rsync onto the
array. After several crashes I tried a simple "dd if=/dev/zero of=./file"
and after writing ~33GB the machine rebooted (the panic details below are
from this reboot)
Details follow:
# ls -l /fs/VLargeZeroFile
-rw-r--r-- 1 root wheel 35446063104 Nov 29 15:00 /fs/file
# gpt -r -v show /dev/da0
gpt show: /dev/da0: mediasize=5597405642752; sectorsize=512;
blocks=10932432896
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 10932432829 1 GPT part - FreeBSD UFS/UFS2
10932432863 32 Sec GPT table
10932432895 1 Sec GPT header
# df -h /fs
Filesystem Size Used Avail Capacity Mounted on
/dev/da0p1 4.9T 897G 3.7T 19% /fs
# df -ki /fs
Filesystem 1K-blocks Used Avail Capacity iused ifree %iused
Mounted on
/dev/da0p1 5294245800 940234932 3930471204 19% 2190679 681971367 0%
/fs
Error messages before panic:
Nov 29 12:29:46 mach kernel: pid 6749 (bsdtar), uid 0 inumber 234766339 on
/fs: filesystem full
Nov 29 14:19:00 mach kernel: pid 34204 (pax), uid 0 inumber 505543685 on
/fs: filesystem full
Dumpfs header:
magic 19540119 (UFS2) time Mon Nov 29 15:23:41 2004
superblock location 65536 id [ 419208fe aae47fbc ]
ncg 29049 size 2733108207 blocks 2647122900
bsize 16384 shift 14 mask 0xffffc000
fsize 2048 shift 11 mask 0xfffff800
frag 8 shift 3 fsbtodb 2
minfree 8% optim time symlinklen 120
maxbsize 16384 maxbpg 2048 maxcontig 8 contigsumsize 8
nbfree 272113785 ndir 267986 nifree 681971367 nffree 95154
bpg 11761 fpg 94088 ipg 23552
nindir 2048 inopb 64 maxfilesize 140806241583103
sbsize 2048 cgsize 16384 csaddr 3000 cssize 464896
sblkno 40 cblkno 48 iblkno 56 dblkno 3000
cgrotor 22824 fmod 0 ronly 0 clean 0
avgfpdir 64 avgfilesize 16384
flags none
fsmnt /fs
volname swuid 0
info file contents:
Good dump found on device /dev/da1s1e
Architecture: i386
Architecture version: 1
Dump length: 2147483648B (2048 MB)
Blocksize: 512
Dumptime: Mon Nov 29 15:01:10 2004
Hostname: mach.example.com
Versionstring: FreeBSD 5.3-STABLE #0: Fri Nov 12 13:05:18 UTC 2004
root@mach.example.com:/usr/obj/usr/src/sys/SMP
Panicstring: ffs_clusteralloc: allocated out of group
Bounds: 0
Backtrace:
#0 0xc060ce82 in doadump ()
#1 0xc060d47b in boot ()
#2 0xc060d7a1 in panic ()
#3 0xc073445e in ffs_clusteralloc ()
#4 0xc0733680 in ffs_hashalloc ()
#5 0xc07329ea in ffs_reallocblks_ufs2 ()
#6 0xc073205a in ffs_reallocblks ()
#7 0xc0657e7c in cluster_write ()
#8 0xc074c350 in ffs_write ()
#9 0xc066bf10 in vn_write ()
#10 0xc062d624 in dofilewrite ()
#11 0xc062d4d1 in write ()
#12 0xc07bb07f in syscall ()
#13 0xc07a8a0f in Xint0x80_syscall ()
Kernel is the default SMP kernel and sources are from 28th Nov 2004.
I assume a proper debug kernel with symbols would be more helpful, but I
just wanted to know if this was a known bug - or something I have done
wrong, first.
Other than that is there anything else I can provide to help find this bug?
Thanks
Henry
From owner-freebsd-fs@FreeBSD.ORG Fri Dec 3 20:11:22 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 0881716A4CE
for <freebsd-fs@freebsd.org>; Fri, 3 Dec 2004 20:11:22 +0000 (GMT)
Received: from mailfe05.swip.net (mailfe05.swip.net [212.247.154.129])
by mx1.FreeBSD.org (Postfix) with ESMTP id 0405D43D2D
for <freebsd-fs@freebsd.org>; Fri, 3 Dec 2004 20:11:21 +0000 (GMT)
(envelope-from thn@saeab.se)
X-T2-Posting-ID: v8Qc5gTTFq+hMtTEBMvVyQ==
Received: from [213.100.91.82] (HELO scatcat.thn.saeab.se)
by mailfe05.swip.net (CommuniGate Pro SMTP 4.2.6)
with ESMTP id 38840953; Fri, 03 Dec 2004 21:11:19 +0100
Received: from saeab.se (home [10.1.0.1])iB3KBJuA008450;
Fri, 3 Dec 2004 21:11:19 +0100 (CET) (envelope-from thn@saeab.se)
Message-ID: <41B0C899.C005AE1E@saeab.se>
Date: Fri, 03 Dec 2004 21:12:09 +0100
From: Thomas Nystrom <thn@saeab.se>
Organization: Sv. Aktuell Elektronik AB
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: sv,en
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: Dead vnode locking against itself
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Dec 2004 20:11:22 -0000
I'm trying to get ARLA to work stable on FreeBSD (5.3-RELEASE) but have
found that it sometimes hangs: A process gets stuck in 'ckvnlk' state.
I have found someting strange (probably a bug) but I need a second
opinion.
I patched fs/deadfs/dead_vnops so it does a panic when it tries to go
into ckvnlk state and found that it seems to lock against itself.
Part of the backtrace:
#10 0xc04c6f8f in panic (fmt=0x296 <Address 0x296 out of bounds>)
at /usr/src/sys/kern/kern_shutdown.c:537
#11 0xc0483de3 in chkvnlock (vp=0xc239d420) at /usr/src/sys/fs/deadfs/dead_vnops.c:248
#12 0xc0483d0a in dead_lock (ap=0xdb344914) at /usr/src/sys/fs/deadfs/dead_vnops.c:210
#13 0xc0515f8f in vclean (vp=0xc239d420, flags=8, td=0xc1c3d640) at vnode_if.h:1013
#14 0xc0516525 in vgonel (vp=0xc239d420, td=0xc1c3d640)
at /usr/src/sys/kern/vfs_subr.c:2701
#15 0xc0513051 in vtryrecycle (vp=0xc239d420) at /usr/src/sys/kern/vfs_subr.c:720
#16 0xc051327a in getnewvnode (tag=0xc0645372 "ufs", mp=0xc1918000, vops=0x0, vpp=0x0)
at /usr/src/sys/kern/vfs_subr.c:783
---Type <return> to continue, or q <return> to quit---
#17 0xc05bac67 in ffs_vget (mp=0xc1918000, ino=427054, flags=2, vpp=0xdb344a84)
at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1230
#18 0xc05c1c64 in ufs_lookup (ap=0xdb344b40) at /usr/src/sys/ufs/ufs/ufs_lookup.c:599
#19 0xc05c7eaf in ufs_vnoperate (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2816
#20 0xc050b5d6 in vfs_cache_lookup (ap=0x0) at vnode_if.h:82
#21 0xc05c7eaf in ufs_vnoperate (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2816
#22 0xc050fcf3 in lookup (ndp=0xdb344c30) at vnode_if.h:52
#23 0xc050f778 in namei (ndp=0xdb344c30) at /usr/src/sys/kern/vfs_lookup.c:181
#24 0xc051a9f6 in lstat (td=0xc1c3d640, uap=0xdb344d14)
at /usr/src/sys/kern/vfs_syscalls.c:2069
#25 0xc060e093 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134609408, tf_esi = 134609480, tf_ebp
= -1077941208, tf_isp = -617329292, tf_ebx = 672396780, tf_edx = 134561792, tf_ecx = 0, tf
_eax = 190, tf_trapno = 12, tf_err = 2, tf_eip = 671905847, tf_cs = 31, tf_eflags = 658, t
f_esp = -1077941364, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1001
#26 0xc06015ff in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:201
If I look at the source I can see that in sys/kern/vfs_subr.c:2696
(in vgonel) the vnode is locked by VI_XLOCK. Later on (via vclean)
dead_lock is called and founds that the vnode is locked. It then
waits for it to be unlocked and the results is a hanged process.
What have I missed or have I found a bug?
/thn
--
---------------------------------------------------------------
Svensk Aktuell Elektronik AB Thomas Nyström
Box 10 Phone: +46 8 35 92 85
S-191 21 Sollentuna Fax: +46 8 35 92 86
Sweden Email: thn@saeab.se
---------------------------------------------------------------