From owner-freebsd-fs@FreeBSD.ORG Sun May 31 18:05:28 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72E20106566B for ; Sun, 31 May 2009 18:05:28 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ew0-f212.google.com (mail-ew0-f212.google.com [209.85.219.212]) by mx1.freebsd.org (Postfix) with ESMTP id 09DBD8FC0A for ; Sun, 31 May 2009 18:05:27 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by ewy8 with SMTP id 8so3897855ewy.43 for ; Sun, 31 May 2009 11:05:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=ZktnYyEwgocTJHYCzjaxTmIukAGFKsLKwCkHLiKgTVg=; b=Yg3PZpvjZ8jmksqFvU+VxB69gpIMdsSQt/fl2p8VDhWyN246HJKiduP0ln/ficVZ+r khtN8+r+VijHHsc7WZC3QbnUTmx5RDozb63FjPmCjZXuWruA9N4ojZdpI2xmGDsF6SiT vMxJSdfj4aTBZFlZm1Lfn/kMWmHyzdRFV3CK8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=EOGIcBQOvNfhvRy/5XW2hXd9ZZd0RJ0sRZwDlEB6Yd8eyqfJ82J0wXkrqp7NqArbL3 gr/6M4BUrIg4m3AYB+bs9GQrTVAdKGZJVz3El4hM1mI2RPxHxSnWVXciCAFt0QRtgiBj QYVUw5xqukco/1Ht1jYrRMiTUJdCw0VF33oHk= MIME-Version: 1.0 Received: by 10.210.39.2 with SMTP id m2mr5022947ebm.38.1243793126945; Sun, 31 May 2009 11:05:26 -0700 (PDT) Date: Sun, 31 May 2009 14:05:26 -0400 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS and syslog X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 18:05:28 -0000 Can ZFS be made to log these events? Am I missing a knob? Particularly the first one, UFS does. The second case is not as critical since the ATA and GEOM susbsystems complain. But it would be nice to have ZFS emit as well whenever it increments some sensor counter or state change somewhere, because there may not always be an underlying msg from a subsystem. - Disk full dd if=/dev/urandom of=zero bs=1m [no syslog msg] ### No space to do an rm? The dataset uses gzip and sha256. # df tank/foo 4368000 4368000 0 100% 43999 0 100% /foo # ls -lsi zero 4645 1791445 -rw-r--r-- 1 xxxx xxxx 1792802816 May 31 12:14 zero # rm -f zero rm: zero: No space left on device # :> zero # ls -lsi zero 4645 1 -rw-r--r-- 1 xxxx xxxx 0 May 31 12:19 zero # rm zero [ok] - Faults ad3: FAILURE - READ_DMA48 timed out LBA= GEOM_ELI: g_eli_read_done() failed ad3.eli[READ(offset=, length=65536)] NAME STATE READ WRITE CKSUM tank ONLINE 1 0 0 ad3.eli ONLINE 1 0 0 [no syslog msg] From owner-freebsd-fs@FreeBSD.ORG Sun May 31 18:25:37 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB8F51065672 for ; Sun, 31 May 2009 18:25:37 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ew0-f212.google.com (mail-ew0-f212.google.com [209.85.219.212]) by mx1.freebsd.org (Postfix) with ESMTP id 560978FC13 for ; Sun, 31 May 2009 18:25:37 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by ewy8 with SMTP id 8so3905221ewy.43 for ; Sun, 31 May 2009 11:25:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=4SqknlYz8GqZ4YlocUuuPKnKgCdoFY8UkDmK2PSI6so=; b=IRs6t/eCI6+XFQggaKmiGPZ2mWoAIDbdQqIIk8YE+FWM/D9WpE43hO9lIOFpAccyBH 18RekU6a9ZygskULIaHkmHgh1udvkYkrLgxMm6yihOGhJWkVIB2n/xnubBXNWI/c/0qo SvbyN4M1zVXr6FBw9lFaC1HJ0C839AhasYmac= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=l9VzepTo3OuzVa26mgIc/fYMdcNuoINXemD0RYEhASuL625S8HbeQadf1OPx8Dmdi6 OeZGZynf5VzJ5Sdwvcpq6pqCrXfzM4IgjXASI8mjEGrRgdhCqxIgJTwPVbm9qwAsCtDd r1U9iUoSTvJlovIgHE/i1i4J8OfgBbcXtwY68= MIME-Version: 1.0 Received: by 10.210.38.5 with SMTP id l5mr3038631ebl.16.1243794336231; Sun, 31 May 2009 11:25:36 -0700 (PDT) Date: Sun, 31 May 2009 14:25:36 -0400 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS and idprio X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 18:25:38 -0000 On an i386 with 1GB ram and P4 2.x GHz single core with arc_max at 64MiB and everything else from RELENG_7_1_0_RELEASE left at default, with this disk layering: PDC20269@100 > PATA > geli > zfs [gzip sha256]. The system become unusable slow when doing heavy sequential disk IO. Such as copy 50G data, zpool scrub, etc. These two processes [*] eat the cpu. I did idprio 31 on them and got 'ki-1' in the nice column [was '-'] and seemed some responsiveness back after a few minutes. Should I be able to nice these kernel threads? Any other way to drop their priority? What is 'ki-1'? Top doesn't seem to show that field right as with say nice -20 sleep 60? Sorted by time: 11 root 1 171 ki31 0K 8K RUN 25.2H 93.90% idle: cpu0 * 594 root 1 -8 - 0K 8K geli:w 321:27 0.68% g_eli[0] ad4 * 695 root 1 -16 - 0K 24K tq->tq 252:33 0.00% spa_zio_intr_1 * 597 root 1 -8 - 0K 8K geli:w 181:52 0.00% g_eli[0] ad5 * 729 root 1 101 - 0K 24K tq->tq 131:01 0.00% spa_zio_intr_1 758 iso 1 44 0 172M 49572K select 62:43 0.00% XFree86 740 root 1 -16 - 0K 24K tx->tx 44:00 0.00% txg_thread_enter Not under load: load averages: 0.12, 0.40, 0.51 up 2+01:11:50 14:19:22 164 processes: 4 running, 141 sleeping, 19 waiting CPU: 0.8% user, 0.0% nice, 15.0% system, 0.8% interrupt, 83.5% idle Mem: 147M Active, 146M Inact, 265M Wired, 24M Cache, 47M Buf, 410M Free From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 11:06:50 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A59F1065673 for ; Mon, 1 Jun 2009 11:06:50 +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 7C76A8FC28 for ; Mon, 1 Jun 2009 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n51B6oTD021053 for ; Mon, 1 Jun 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n51B6no8021049 for freebsd-fs@FreeBSD.org; Mon, 1 Jun 2009 11:06:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Jun 2009 11:06:49 GMT Message-Id: <200906011106.n51B6no8021049@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/135039 fs [zfs] mkstemp() fails over NFS when server uses ZFS (7 f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels f kern/133020 fs [zfs] [panic] inappropriate panic caused by zfs. Pani o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132337 fs [zfs] [panic] kernel panic in zfs_fuid_create_cred o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129148 fs [zfs] [panic] panic on concurrent writing & rollback o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o kern/122173 fs [zfs] [panic] Kernel Panic if attempting to replace a o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o kern/121770 fs [zfs] ZFS on i386, large file or heavy I/O leads to ke o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o bin/120288 fs zfs(8): "zfs share -a" does not send SIGHUP to mountd f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o misc/118855 fs [zfs] ZFS-related commands are nonfunctional in fixit o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118320 fs [zfs] [patch] NFS SETATTR sometimes fails to set file o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o kern/113180 fs [zfs] Setting ZFS nfsshare property does not cause inh o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist f kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 137 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 12:16:20 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57387106566B for ; Mon, 1 Jun 2009 12:16:20 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by mx1.freebsd.org (Postfix) with ESMTP id 24D238FC13 for ; Mon, 1 Jun 2009 12:16:19 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-ma04.mx.aol.com (imo-ma04.mx.aol.com [64.12.78.139]) by imo-d06.mx.aol.com (v107.10) with ESMTP id RELAYIN3-44a23c33e3c4; Mon, 01 Jun 2009 08:02:06 -0400 Received: from samankaya@netscape.net by imo-ma04.mx.aol.com (mail_out_v40_r1.5.) id n.c46.5803b6e6 (37116) for ; Mon, 1 Jun 2009 08:02:04 -0400 (EDT) Received: from smtprly-da03.mx.aol.com (smtprly-da03.mx.aol.com [205.188.249.146]) by cia-ma01.mx.aol.com (v123.4) with ESMTP id MAILCIAMA012-5bbb4a23c3342cb; Mon, 01 Jun 2009 08:02:03 -0400 Received: from webmail-md07 (webmail-md07.webmail.aol.com [64.12.170.145]) by smtprly-da03.mx.aol.com (v123.4) with ESMTP id MAILSMTPRLYDA032-5bbb4a23c3342cb; Mon, 01 Jun 2009 08:01:56 -0400 To: freebsd-fs@freebsd.org Date: Mon, 01 Jun 2009 08:01:56 -0400 X-MB-Message-Source: WebUI X-AOL-IP: 64.12.78.139 X-MB-Message-Type: User MIME-Version: 1.0 From: samankaya@netscape.net X-Mailer: AIM WebMail 42952-STANDARD Received: from 81.178.2.118 by webmail-md07.sysops.aol.com (64.12.170.145) with HTTP (WebMailUI); Mon, 01 Jun 2009 08:01:56 -0400 Message-Id: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 12:16:20 -0000 Hello all, This is my first post and first time on a mailing list for a very long time :) I am just about to switch my Debian Linux install over to a dual boot between Solaris Express Community Edition (SXCE) and FreeBSD 7.2. Currently my setup is as follows: hda1 - ext3 hdb1 - ext3 Linux root / hdb2 - ext3 Linux home /home Because of the lack of space in my network and the fact that the master IDE drive is 250GB and the slave IDE drive is 160GB I wanted to wipe / on hdb1 and reformat to UFS2 and install FreeBSD. However would I be able to then write to UFS of Solaris as I will reformat the master to UFS for SXCE. I read on a forum already that BSD cannot write to ext3 only ext2 and if it did write to ext3 it would be without the journal. So I am not sure if writing to ext3 from BSD is a good idea either? The plan though at least is to write to UFS so that I can I can just bounce my data back and forth, so when it comes down to reformatting the ext3 /home partition I won't loose any of my information! I do not have a SAN or NAS system or even enough space in my servers for NFS transfer which is why I need to take these measures in the first place..... I hope someone has a response for my dilemma - many thanks, Kaya From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 18:04:15 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24517106566C for ; Mon, 1 Jun 2009 18:04:15 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-d23.mx.aol.com (imo-d23.mx.aol.com [205.188.139.137]) by mx1.freebsd.org (Postfix) with ESMTP id E31548FC1B for ; Mon, 1 Jun 2009 18:04:14 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-ma04.mx.aol.com (imo-ma04.mx.aol.com [64.12.78.139]) by imo-d23.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a241815344; Mon, 01 Jun 2009 14:04:05 -0400 Received: from samankaya@netscape.net by imo-ma04.mx.aol.com (mail_out_v40_r1.5.) id n.bbb.4f2e2976 (37568); Mon, 1 Jun 2009 14:04:01 -0400 (EDT) Received: from smtprly-da01.mx.aol.com (smtprly-da01.mx.aol.com [205.188.249.144]) by cia-mb04.mx.aol.com (v123.4) with ESMTP id MAILCIAMB045-5bad4a24180f276; Mon, 01 Jun 2009 14:04:00 -0400 Received: from WEBMAIL-MZ02 (webmail-mz02.sim.aol.com [64.12.222.33]) by smtprly-da01.mx.aol.com (v123.4) with ESMTP id MAILSMTPRLYDA014-5bad4a24180f276; Mon, 01 Jun 2009 14:03:59 -0400 References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> <4a2414be.02578c0a.7321.13fc@mx.google.com> To: sarawgi.aditya@gmail.com Date: Mon, 01 Jun 2009 14:03:59 -0400 X-AOL-IP: 64.12.78.139 In-Reply-To: <4a2414be.02578c0a.7321.13fc@mx.google.com> X-MB-Message-Source: WebUI Received: from 81.149.17.147 by WEBMAIL-MZ02.sysops.aol.com (64.12.222.33) with HTTP (WebMailUI); Mon, 01 Jun 2009 14:03:59 -0400 MIME-Version: 1.0 From: samankaya@netscape.net X-MB-Message-Type: User X-Mailer: AOL Webmail 42952-STANDARD Message-Id: <8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 18:04:15 -0000 Many thanks for the response! That solves the ext3 fs issue, how about UFS and Solaris as that is probably more important at this stage? Baring in mind Solaris uses UFS1 while BSD is on UFS2! Regards, Kaya -----Original Message----- From: Aditya Sarawgi To: samankaya@netscape.net CC: freebsd-fs@freebsd.org Sent: Mon, 1 Jun 2009 13:19 Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? On Mon, Jun 01, 2009 at 08:01:56AM -0400, samankaya@netscape.net wrote: > Hello all, > > This is my first post and first time on a mailing list for a very long time :) > > I am just about to switch my Debian Linux install over to a dual boot between Solaris Express Community Edition (SXCE) and FreeBSD 7.2. > > Currently my setup is as follows: > > hda1 - ext3 > hdb1 - ext3 Linux root / > hdb2 - ext3 Linux home /home > > Because of the lack of space in my network and the fact that the master IDE drive is 250GB and the slave IDE drive is 160GB I wanted to wipe / on hdb1 and reformat to UFS2 and install FreeBSD. > > However would I be able to then write to UFS of Solaris as I will reformat the master to UFS for SXCE. I read on a forum already that BSD cannot write to ext3 only ext2 and if it did write to ext3 it would be without the journal. So I am not sure if writing to ext3 from BSD is a good idea either? > > The plan though at least is to write to UFS so that I can I can just bounce my data back and forth, so when it comes down to reformatting the ext3 /home partition I won't loose any of my information! > > I do not have a SAN or NAS system or even enough space in my servers for NFS transfer which is why I need to take these measures in the first place..... > > I hope someone has a response for my dilemma - many thanks, > > Kaya > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Yes currently journaling is not supported by ext2fs but you can read & write safely if the inode size of your ext2/ext3 partition is 128. If the inode size is different from 128 (which is common nowdays) then you can use the following patch http://pflog.net/~floyd/ext2fs.diff Cheers, Aditya Sarawgi ________________________________________________________________________ AOL Email goes Mobile! You can now read your AOL Emails whilst on the move. Sign up for a free AOL Email account with unlimited storage today. From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 18:14:51 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6264C1065712 for ; Mon, 1 Jun 2009 18:14:51 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id 31C8A8FC1E for ; Mon, 1 Jun 2009 18:14:50 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: by rv-out-0506.google.com with SMTP id k40so3070497rvb.43 for ; Mon, 01 Jun 2009 11:14:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=/k27TFJmyMYXuOfIvw5HRWmf+Svjs3NkwXh6kpSCbik=; b=KkydHV2GhMGnQJtOcJ5lTPe/8LWQjAgjgVEUX9jEv5vrRZUCa+mgmCgskmpKGXPSZc YesjuqKzjFxvHxpxV2jbala+yRARszrobNOrxoU9VyY0u03G+sSfouD5oUxWJr7qpwWm HkTIG10ZpFrncwtt2mjyEbg8Yn+o+HMwPC7Zw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=nyCoR9pWBmyOqDVjaFLcyL8dBIXUbkNezmH1KI5Z2y6xlzWHIpT6kt+C2fIUiJslQy cvquNvr/z/f8W9zpXyYvuKBiDttypfheE5QyvsYjAUHN8OZt4oE5IqAAJ+GDMYlkwEdI CTMBNAWAe3iFhiQ1xLsI45nQ2zznGYVIrwz8k= Received: by 10.140.134.15 with SMTP id h15mr7443567rvd.156.1243878591564; Mon, 01 Jun 2009 10:49:51 -0700 (PDT) Received: from ([121.242.97.136]) by mx.google.com with ESMTPS id k2sm14609146rvb.4.2009.06.01.10.49.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 10:49:50 -0700 (PDT) Date: Mon, 1 Jun 2009 17:49:50 +0530 From: Aditya Sarawgi To: samankaya@netscape.net Message-ID: <4a2414be.02578c0a.7321.13fc@mx.google.com> References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 18:14:52 -0000 On Mon, Jun 01, 2009 at 08:01:56AM -0400, samankaya@netscape.net wrote: > Hello all, > > This is my first post and first time on a mailing list for a very long time :) > > I am just about to switch my Debian Linux install over to a dual boot between Solaris Express Community Edition (SXCE) and FreeBSD 7.2. > > Currently my setup is as follows: > > hda1 - ext3 > hdb1 - ext3 Linux root / > hdb2 - ext3 Linux home /home > > Because of the lack of space in my network and the fact that the master IDE drive is 250GB and the slave IDE drive is 160GB I wanted to wipe / on hdb1 and reformat to UFS2 and install FreeBSD. > > However would I be able to then write to UFS of Solaris as I will reformat the master to UFS for SXCE. I read on a forum already that BSD cannot write to ext3 only ext2 and if it did write to ext3 it would be without the journal. So I am not sure if writing to ext3 from BSD is a good idea either? > > The plan though at least is to write to UFS so that I can I can just bounce my data back and forth, so when it comes down to reformatting the ext3 /home partition I won't loose any of my information! > > I do not have a SAN or NAS system or even enough space in my servers for NFS transfer which is why I need to take these measures in the first place..... > > I hope someone has a response for my dilemma - many thanks, > > Kaya > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Yes currently journaling is not supported by ext2fs but you can read & write safely if the inode size of your ext2/ext3 partition is 128. If the inode size is different from 128 (which is common nowdays) then you can use the following patch http://pflog.net/~floyd/ext2fs.diff Cheers, Aditya Sarawgi From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 19:49:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AC2E106564A for ; Mon, 1 Jun 2009 19:49:39 +0000 (UTC) (envelope-from matt@corp.spry.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 060468FC14 for ; Mon, 1 Jun 2009 19:49:38 +0000 (UTC) (envelope-from matt@corp.spry.com) Received: by rv-out-0506.google.com with SMTP id k40so3088922rvb.43 for ; Mon, 01 Jun 2009 12:49:38 -0700 (PDT) Received: by 10.140.144.1 with SMTP id r1mr7247090rvd.131.1243884330451; Mon, 01 Jun 2009 12:25:30 -0700 (PDT) Received: from mattintosh.spry.com (isaid.donotdelete.com [64.79.222.10]) by mx.google.com with ESMTPS id f42sm16434604rvb.51.2009.06.01.12.25.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 12:25:30 -0700 (PDT) Message-Id: <11304BBC-F819-476F-8D9E-CCD622894878@spry.com> From: Matt Simerson To: freebsd-fs@freebsd.org In-Reply-To: <8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Jun 2009 12:25:28 -0700 References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> <4a2414be.02578c0a.7321.13fc@mx.google.com> <8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> X-Mailer: Apple Mail (2.929.2) Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 19:49:39 -0000 On Jun 1, 2009, at 11:03 AM, samankaya@netscape.net wrote: > Many thanks for the response! > > That solves the ext3 fs issue, how about UFS and Solaris as that is > probably more important at this stage? > > Baring in mind Solaris uses UFS1 while BSD is on UFS2! FreeBSD can format disks with UFS1 or UFS2, but that probably won't help you much. http://en.wikipedia.org/wiki/Unix_File_System "Vendors of some commercial Unix systems, such as SunOS/Solaris, System V Release 4, HP-UX, and Tru64 UNIX, have adopted UFS. Most of them adapted UFS to their own uses, adding proprietary extensions that may not be recognized by other vendors' versions of Unix. Surprisingly, many have continued to use the original block size and data field widths as the original UFS, so some degree of (read) compatibility remains across platforms." Consider instead running FreeBSD 8 (or 7.3, if you can wait) with Solaris, and using a ZFS rel 13 partition as the shared medium between them. Many years ago, when I did wanted a shared data partition between switch booted OS platforms, I used a FAT32 partition. These days, virtual machines make it much, much easier. Matt From owner-freebsd-fs@FreeBSD.ORG Mon Jun 1 23:45:31 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7478E106566C for ; Mon, 1 Jun 2009 23:45:31 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-m13.mail.aol.com (imo-m13.mx.aol.com [64.12.143.101]) by mx1.freebsd.org (Postfix) with ESMTP id 3C2968FC1E for ; Mon, 1 Jun 2009 23:45:31 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-da01.mx.aol.com (imo-da01.mx.aol.com [205.188.169.199]) by imo-m13.mail.aol.com (v107.10) with ESMTP id RELAYIN2-34a24680c222; Mon, 01 Jun 2009 19:45:16 -0400 Received: from samankaya@netscape.net by imo-da01.mx.aol.com (mail_out_v40_r1.5.) id n.c20.5b6a791b (37565); Mon, 1 Jun 2009 19:45:06 -0400 (EDT) Received: from smtprly-ma02.mx.aol.com (smtprly-ma02.mx.aol.com [64.12.207.141]) by cia-mb04.mx.aol.com (v123.4) with ESMTP id MAILCIAMB042-5c4c4a246800341; Mon, 01 Jun 2009 19:45:05 -0400 Received: from webmail-mh45 (webmail-mh45.sim.aol.com [64.12.232.140]) by smtprly-ma02.mx.aol.com (v123.4) with ESMTP id MAILSMTPRLYMA022-5c4c4a246800341; Mon, 01 Jun 2009 19:45:04 -0400 References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com><4a2414be.02578c0a.7321.13fc@mx.google.com><8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> <11304BBC-F819-476F-8D9E-CCD622894878@spry.com> To: matt@corp.spry.com Date: Mon, 01 Jun 2009 19:45:04 -0400 X-AOL-IP: 205.188.169.199 In-Reply-To: <11304BBC-F819-476F-8D9E-CCD622894878@spry.com> X-MB-Message-Source: WebUI Received: from 81.178.2.118 by webmail-mh45.sysops.aol.com (64.12.232.140) with HTTP (WebMailUI); Mon, 01 Jun 2009 19:45:04 -0400 MIME-Version: 1.0 From: samankaya@netscape.net X-MB-Message-Type: User X-Mailer: AIM WebMail 42952-STANDARD Message-Id: <8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 23:45:31 -0000 Many thanks for all responses :-) Sorry for the late reply I was in a Cisco CCNA class for the evening and took a chapter test too - achieved 93% though which is not bad! Matt, thanks for the WikiPedia alert I discovered that just before writing to the mailing list taking its advice: "research thoroughly before using a filesystem between OS's" I however a little disappointed that I cannot use UFS to 'bounce' files between BSD and Solaris. Matt, you also mention ZFS rel 13! Is this teh version that comes with Solaris? We maybe back at square 1 with the UFS BSD/Solaris adaptation again :-( I guess in my situation really the alternative seems to be backing things up onto external ext3 hard drive and reading that information into BSD..... or using NFS which at the moment isn't the best option as it would be a bit tedious to boot up a VM every time I wanted to swap between Solaris and BSD! "These days, virtual machines make it much, much easier. " yes that is true if one has the hardware and software to run them. Unfortunately I am on a Pentium IV with only 1GB or RAM which won't even support ZFS file system well, which is why I'm so apprehensive to install ZFS with my Solaris build in the first place and why I revert to the old UFS file system. Hmm..... the only way maybe just to install Sun's Virual Box with 'virtual' BSD for the transferring of files between the hardware installed BSD and Solaris running NFS server? Ouch! Not sure if there are any free Hypervisors out there? VMware and Citrix you have to pay for and even Sun's xVM I think too :-( What do you guys think is my best solution here? Probably what I've already covered right? Kaya -----Original Message----- From: Matt Simerson To: freebsd-fs@freebsd.org Sent: Mon, 1 Jun 2009 10:25 pm Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? On Jun 1, 2009, at 11:03 AM, samankaya@netscape.net wrote:? ? > Many thanks for the response!? >? > That solves the ext3 fs issue, how about UFS and Solaris as that is > probably more important at this stage?? >? > Baring in mind Solaris uses UFS1 while BSD is on UFS2!? ? FreeBSD can format disks with UFS1 or UFS2, but that probably won't help you much.? ? http://en.wikipedia.org/wiki/Unix_File_System? ? ? "Vendors of some commercial Unix systems, such as SunOS/Solaris, System V Release 4, HP-UX, and Tru64 UNIX, have adopted UFS. Most of them adapted UFS to their own uses, adding proprietary extensions that may not be recognized by other vendors' versions of Unix. Surprisingly, many have continued to use the original block size and data field widths as the original UFS, so some degree of (read) compatibility remains across platforms."? ? Consider instead running FreeBSD 8 (or 7.3, if you can wait) with Solaris, and using a ZFS rel 13 partition as the shared medium between them. Many years ago, when I did wanted a shared data partition between switch booted OS platforms, I used a FAT32 partition. These days, virtual machines make it much, much easier.? ? Matt? _______________________________________________? freebsd-fs@freebsd.org mailing list? http://lists.freebsd.org/mailman/listinfo/freebsd-fs? To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"? From owner-freebsd-fs@FreeBSD.ORG Tue Jun 2 02:13:29 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 696A5106566C; Tue, 2 Jun 2009 02:13:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3EA728FC14; Tue, 2 Jun 2009 02:13:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n522DSvW023558; Tue, 2 Jun 2009 02:13:28 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n522DS1R023554; Tue, 2 Jun 2009 02:13:28 GMT (envelope-from linimon) Date: Tue, 2 Jun 2009 02:13:28 GMT Message-Id: <200906020213.n522DS1R023554@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135050: [zfs] ZFS clears/hides disk errors on reboot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 02:13:29 -0000 Old Synopsis: ZFS clears/hides disk errors on reboot New Synopsis: [zfs] ZFS clears/hides disk errors on reboot Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Jun 2 02:13:13 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135050 From owner-freebsd-fs@FreeBSD.ORG Tue Jun 2 07:44:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B52F01065670 for ; Tue, 2 Jun 2009 07:44:49 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 704A68FC23 for ; Tue, 2 Jun 2009 07:44:49 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 1D4FB19E044; Tue, 2 Jun 2009 09:44:46 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D54B019E043; Tue, 2 Jun 2009 09:44:43 +0200 (CEST) Message-ID: <4A24D86C.8040700@quip.cz> Date: Tue, 02 Jun 2009 09:44:44 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: samankaya@netscape.net References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com><4a2414be.02578c0a.7321.13fc@mx.google.com><8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> <11304BBC-F819-476F-8D9E-CCD622894878@spry.com> <8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com> In-Reply-To: <8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 07:44:50 -0000 samankaya@netscape.net wrote: [...] > Matt, thanks for the WikiPedia alert I discovered that just before writing to the mailing list taking its advice: "research thoroughly before using a filesystem between OS's" > > I however a little disappointed that I cannot use UFS to 'bounce' files between BSD and Solaris. Matt, you also mention ZFS rel 13! Is this teh version that comes with Solaris? We maybe back at square 1 with the UFS BSD/Solaris adaptation again :-( ZFS version 13 is the version used in latest FreeBSD (8-CURRENT and 7-STABLE). If you will use this version, you can read & write to it from FreeBSD and Solaris / OpenSolaris. > I guess in my situation really the alternative seems to be backing things up onto external ext3 hard drive and reading that information into BSD..... or using NFS which at the moment isn't the best option as it would be a bit tedious to boot up a VM every time I wanted to swap between Solaris and BSD! > > "These days, virtual machines make it much, much easier. " yes that is true if one has the hardware and software to run them. Unfortunately I am on a Pentium IV with only 1GB or RAM which won't even support ZFS file system well, which is why I'm so apprehensive to install ZFS with my Solaris build in the first place and why I revert to the old UFS file system. > > Hmm..... the only way maybe just to install Sun's Virual Box with 'virtual' BSD for the transferring of files between the hardware installed BSD and Solaris running NFS server? Ouch! > > Not sure if there are any free Hypervisors out there? VMware and Citrix you have to pay for and even Sun's xVM I think too :-( > > What do you guys think is my best solution here? Probably what I've already covered right? If you need some hypervisor, VMware provides ESXi for free and Citrix has XenServer for free too. Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Tue Jun 2 12:01:10 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E873106568D; Tue, 2 Jun 2009 12:01:10 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: from mail-qy0-f173.google.com (mail-qy0-f173.google.com [209.85.221.173]) by mx1.freebsd.org (Postfix) with ESMTP id 0E6E58FC27; Tue, 2 Jun 2009 12:01:09 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: by qyk3 with SMTP id 3so11970617qyk.3 for ; Tue, 02 Jun 2009 05:01:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=z+tcS0Dj2yy432TcqMIH/Xkdg/maxyvNwecpnCv6Pds=; b=pKgPaHgerrzPpSHNWUl0/VqMvy79bXT+gaaTjHNlCyz3orqcrPRr6G1XRgcvz8GfLe CDD/J2lJ21RWVrYVoW7AbvZDtMBTYv/f+aWzJikymJgJxphYel1XgJF2hA6JchTlDezx /GGfVkgKzNT8PkzFTGKENUBlyjWHrcgF7uNsQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=rD+OA8suQKbggwZvOWu6OyiG7wRBTNcfLs+hufzlyhmuGIVxAeUJs9cHAg+RX1IQm5 pzTfbTL4BNeFt3wfZ/Sa3z71DhlVriwRnXRUd0jAzgkmKxvQ8SjN+MK3ho9VglSm3rcv Veb8c7cxepXd9rIyE2ozk7PS4FN8g/P9f9HfM= MIME-Version: 1.0 Received: by 10.229.85.21 with SMTP id m21mr2013931qcl.9.1243944069369; Tue, 02 Jun 2009 05:01:09 -0700 (PDT) In-Reply-To: <4d7dd86f0906020449m43d03311jf7fcae2fbb5339c1@mail.gmail.com> References: <4d7dd86f0906020449m43d03311jf7fcae2fbb5339c1@mail.gmail.com> Date: Tue, 2 Jun 2009 22:01:09 +1000 Message-ID: <4d7dd86f0906020501h1439eb92g15ae886f72f4d226@mail.gmail.com> From: David N To: freebsd-stable , freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Crash with GJournal switcher X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 12:01:12 -0000 2009/6/2 David N : > FreeBSD 7.2-RELEASE > GPT + gmirror + gjournal > > May 31 10:15:48 netserv1 kernel: Fatal trap 9: general protection > fault while in kernel mode > May 31 10:15:48 netserv1 kernel: cpuid =3D 0; apic id =3D 00 > May 31 10:15:48 netserv1 kernel: instruction pointer =A0 =A0=3D 0x8:0xfff= fffff8059f667 > May 31 10:15:48 netserv1 kernel: stack pointer =A0 =A0 =A0 =A0 =A0=3D > 0x10:0xfffffffe801e0a60 > May 31 10:15:48 netserv1 kernel: frame pointer =A0 =A0 =A0 =A0 =A0=3D > 0x10:0xfffffffe801e0a90 > May 31 10:15:48 netserv1 kernel: code segment =A0 =A0 =A0 =A0 =A0 =3D bas= e 0x0, > limit 0xfffff, type 0x1b > May 31 10:15:48 netserv1 kernel: =3D DPL 0, pres 1, long 1, def32 0, gran= 1 > May 31 10:15:48 netserv1 kernel: processor eflags =A0 =A0 =A0 =3D interru= pt > enabled, resume, IOPL =3D 0 > May 31 10:15:48 netserv1 kernel: current process =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0=3D 39 > (g_journal switcher) > > > This caused one of my mirrors to become stale upon reboot. There > wasn't any crash dumps. > > I've got WITNESS compiled at the moment, hopefully a crash/lockup will > show something. Would the gjournal fail if one of the gmirror disks > was faulty? > > Regards > David N > lock order reversal: 1st 0xffffffff80b184c0 sleepq chain (sleepq chain) @ /usr/src/sys/kern/kern_sig.c:2291 2nd 0xffffffff80afb5b0 scrlock (scrlock) @ /usr/src/sys/dev/syscons/syscons.c:2519 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a witness_checkorder() at witness_checkorder+0x565 _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x3d sc_puts() at sc_puts+0x93 sc_cnputc() at sc_cnputc+0x5a cnputc() at cnputc+0x49 putchar() at putchar+0x6b kvprintf() at kvprintf+0x72 printf() at printf+0xa4 witness_checkorder() at witness_checkorder+0x44c _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x3d wakeup() at wakeup+0x11 tdsignal() at tdsignal+0x526 realitexpire() at realitexpire+0x3e softclock() at softclock+0x270 ithread_loop() at ithread_loop+0xe7 fork_exit() at fork_exit+0x112 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xfffffffe8001cd30, rbp =3D 0 --- acquiring duplicate lock of same type: "sleepq chain" 1st sleepq chain @ /usr/src/sys/kern/kern_sig.c:2291 2nd sleepq chain @ /usr/src/sys/kern/subr_sleepqueue.c:232 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a witness_checkorder() at witness_checkorder+0x565 _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x3d wakeup() at wakeup+0x11 tdsignal() at tdsignal+0x526 realitexpire() at realitexpire+0x3e softclock() at softclock+0x270 ithread_loop() at ithread_loop+0xe7 fork_exit() at fork_exit+0x112 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xfffffffe8001cd30, rbp =3D 0 --- From owner-freebsd-fs@FreeBSD.ORG Tue Jun 2 12:21:59 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A61F106564A for ; Tue, 2 Jun 2009 12:21:59 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id 286C98FC24 for ; Tue, 2 Jun 2009 12:21:59 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so4377874qwe.7 for ; Tue, 02 Jun 2009 05:21:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=btLR9IX6D4RbKqhg6h8X02jVOJB8ua7a6JT7c5G4TG0=; b=qjt+Ee62NbvpOkidJ1datZ33UC5y+JOiOdiFt5KbPpvA2xFVAKWjxCiVWHKTaTcN74 1fjSUPK2wwpqTG2qslDrdnKb63wUW2ugqAXSi62vNnSFP0LvaCWy5Ht9nxjgMzFTlVn7 UKUpt0sVbQ5lRGrKskl50eHQ0vZ6euGDiV62c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=M3545DKbZI+NZf+lyrOxNuPTESpF+0gXCD9LBeMfy2CMh6Z5CaaGZ4/WnzxNxngy3M CIyFvsGnCV8aFA1KYyf1nHWAZww+4u6JEzUNb0JpFGL9d4pQcduZQxuCeYkzDCx5/B7p n2teYAT2qlt0rQQaeab2Iu8XcJzIj2v6d19L8= MIME-Version: 1.0 Received: by 10.229.97.19 with SMTP id j19mr1926696qcn.54.1243943363263; Tue, 02 Jun 2009 04:49:23 -0700 (PDT) Date: Tue, 2 Jun 2009 21:49:23 +1000 Message-ID: <4d7dd86f0906020449m43d03311jf7fcae2fbb5339c1@mail.gmail.com> From: David N To: freebsd-stable , freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Crash with GJournal switcher X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 12:21:59 -0000 FreeBSD 7.2-RELEASE GPT + gmirror + gjournal May 31 10:15:48 netserv1 kernel: Fatal trap 9: general protection fault while in kernel mode May 31 10:15:48 netserv1 kernel: cpuid = 0; apic id = 00 May 31 10:15:48 netserv1 kernel: instruction pointer = 0x8:0xffffffff8059f667 May 31 10:15:48 netserv1 kernel: stack pointer = 0x10:0xfffffffe801e0a60 May 31 10:15:48 netserv1 kernel: frame pointer = 0x10:0xfffffffe801e0a90 May 31 10:15:48 netserv1 kernel: code segment = base 0x0, limit 0xfffff, type 0x1b May 31 10:15:48 netserv1 kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 May 31 10:15:48 netserv1 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 31 10:15:48 netserv1 kernel: current process = 39 (g_journal switcher) This caused one of my mirrors to become stale upon reboot. There wasn't any crash dumps. I've got WITNESS compiled at the moment, hopefully a crash/lockup will show something. Would the gjournal fail if one of the gmirror disks was faulty? Regards David N From owner-freebsd-fs@FreeBSD.ORG Tue Jun 2 21:51:24 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 149FA106564A for ; Tue, 2 Jun 2009 21:51:24 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imr-m07.mx.aol.com (imr-m07.mx.aol.com [64.12.138.209]) by mx1.freebsd.org (Postfix) with ESMTP id C405E8FC14 for ; Tue, 2 Jun 2009 21:51:23 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-m07.mx.aol.com (v107.10) with ESMTP id RELAYIN1-24a259daf131; Tue, 02 Jun 2009 17:46:23 -0400 Received: from samankaya@netscape.net by imo-ma02.mx.aol.com (mail_out_v40_r1.5.) id n.cb3.566c49f2 (37544); Tue, 2 Jun 2009 17:46:20 -0400 (EDT) Received: from smtprly-mb01.mx.aol.com (smtprly-mb01.mx.aol.com [64.12.207.148]) by cia-mb02.mx.aol.com (v123.4) with ESMTP id MAILCIAMB025-5c614a259da726d; Tue, 02 Jun 2009 17:46:20 -0400 Received: from WEBMAIL-MB05 (webmail-mb05.webmail.aol.com [64.12.170.153]) by smtprly-mb01.mx.aol.com (v123.4) with ESMTP id MAILSMTPRLYMB017-5c614a259da726d; Tue, 02 Jun 2009 17:46:15 -0400 References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com><4a2414be.02578c0a.7321.13fc@mx.google.com><8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> <11304BBC-F819-476F-8D9E-CCD622894878@spry.com><8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com> <4A24D86C.8040700@quip.cz> To: 000.fbsd@quip.cz Date: Tue, 02 Jun 2009 17:46:15 -0400 X-AOL-IP: 64.12.78.137 In-Reply-To: <4A24D86C.8040700@quip.cz> X-MB-Message-Source: WebUI Received: from 81.178.2.118 by WEBMAIL-MB05.sysops.aol.com (64.12.170.153) with HTTP (WebMailUI); Tue, 02 Jun 2009 17:46:15 -0400 MIME-Version: 1.0 From: samankaya@netscape.net X-MB-Message-Type: User X-Mailer: AIM WebMail 42952-STANDARD Message-Id: <8CBB1E2B0193EB3-124C-ACD@WEBMAIL-MB05.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 21:51:24 -0000 freebsd-fs@freebsd.org Many thanks for all your suggestions and advice!!!! I think I will research into BSD 8 and either use that or wait for BSD 7.3 to come out as I think that BSD 8 might be development although I don't have a problem with that since I am going to install SXCE any way which is testing line of Solaris just under SXDE. I do not like the idea of ZFS file system on my desktop with 1GB or RAM so I guess I will use the larger master drive as ZFS with /home on it and then my smaller slave with UFS and UFS2 on different partitions for Solaris and BSD root / consecutively. Then get them both to use the same swap space and I should be ok....... As for the hyper visors I have researched them and they seem to be really cool with better computer equipment then my desktop, so not for now. Especially since they require 64-bit CPU architecture and 4GB RAM min. I am quite excited as BSD looks really cool and there's of course the great Solaris which I really like too so all is good. I only need to burn about 60GB of DVD's before hand to make this thing happen but it's not a problem, since I have no good backup solution I am always burning DVD's lol. :-) Best regards, Kaya -----Original Message----- From: Miroslav Lachman <000.fbsd@quip.cz> To: samankaya@netscape.net Cc: freebsd-fs@freebsd.org Sent: Tue, 2 Jun 2009 10:44 am Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? samankaya@netscape.net wrote:? [...]? ? > Matt, thanks for the WikiPedia alert I discovered that just before writing to the mailing list taking its advice: "research thoroughly before using a filesystem between OS's"? > > I however a little disappointed that I cannot use UFS to 'bounce' files between BSD and Solaris. Matt, you also mention ZFS rel 13! Is this teh version that comes with Solaris? We maybe back at square 1 with the UFS BSD/Solaris adaptation again :-(? ? ZFS version 13 is the version used in latest FreeBSD (8-CURRENT and 7-STABLE). If you will use this version, you can read & write to it from FreeBSD and Solaris / OpenSolaris.? ? > I guess in my situation really the alternative seems to be backing things up onto external ext3 hard drive and reading that information into BSD..... or using NFS which at the moment isn't the best option as it would be a bit tedious to boot up a VM every time I wanted to swap between Solaris and BSD!? > > "These days, virtual machines make it much, much easier. " yes that is true if one has the hardware and software to run them. Unfortunately I am on a Pentium IV with only 1GB or RAM which won't even support ZFS file system well, which is why I'm so apprehensive to install ZFS with my Solaris build in the first place and why I revert to the old UFS file system.? > > Hmm..... the only way maybe just to install Sun's Virual Box with 'virtual' BSD for the transferring of files between the hardware installed BSD and Solaris running NFS server? Ouch!? > > Not sure if there are any free Hypervisors out there? VMware and Citrix you have to pay for and even Sun's xVM I think too :-(? > > What do you guys think is my best solution here? Probably what I've already covered right?? ? If you need some hypervisor, VMware provides ESXi for free and Citrix has XenServer for free too.? ? Miroslav Lachman? _______________________________________________? freebsd-fs@freebsd.org mailing list? http://lists.freebsd.org/mailman/listinfo/freebsd-fs? To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"? From owner-freebsd-fs@FreeBSD.ORG Wed Jun 3 07:20:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6203F1065675 for ; Wed, 3 Jun 2009 07:20:14 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by mx1.freebsd.org (Postfix) with ESMTP id E4D578FC1D for ; Wed, 3 Jun 2009 07:20:13 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n537K9W1019885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jun 2009 17:20:10 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n537K9kr027844; Wed, 3 Jun 2009 17:20:09 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n537K9YR027843; Wed, 3 Jun 2009 17:20:09 +1000 (EST) (envelope-from peter) Date: Wed, 3 Jun 2009 17:20:09 +1000 From: peterjeremy@optushome.com.au To: samankaya@netscape.net Message-ID: <20090603072009.GA27800@server.vk2pj.dyndns.org> References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com> <4a2414be.02578c0a.7321.13fc@mx.google.com> <8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com> <11304BBC-F819-476F-8D9E-CCD622894878@spry.com> <8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com> <4A24D86C.8040700@quip.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <4A24D86C.8040700@quip.cz> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 07:20:14 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jun-02 09:44:44 +0200, Miroslav Lachman <000.fbsd@quip.cz> wrote: >ZFS version 13 is the version used in latest FreeBSD (8-CURRENT and=20 >7-STABLE). If you will use this version, you can read & write to it from= =20 >FreeBSD and Solaris / OpenSolaris. If you are using Solaris (rather than OpenSolaris), I'd verify exactly what version of ZFS is supported. After installing a fairly recent jumbo patch, my Sol10 server went from ZFS version 4 to version 10 - but that is still well behind FreeBSD. --=20 Peter Jeremy --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkomJCgACgkQ/opHv/APuIfJogCgj5Flh0K0U19EkMK8Ytug78K6 TNEAoINLjSSoAFSCfsXQ2w/azSwNC7Ij =bmOj -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-fs@FreeBSD.ORG Wed Jun 3 07:47:12 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 457071065674 for ; Wed, 3 Jun 2009 07:47:12 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-m13.mail.aol.com (imo-m13.mx.aol.com [64.12.143.101]) by mx1.freebsd.org (Postfix) with ESMTP id 0D4B68FC19 for ; Wed, 3 Jun 2009 07:47:11 +0000 (UTC) (envelope-from samankaya@netscape.net) Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imo-m13.mail.aol.com (v107.10) with ESMTP id RELAYIN3-44a262a7e184; Wed, 03 Jun 2009 03:47:10 -0400 Received: from samankaya@netscape.net by imo-ma02.mx.aol.com (mail_out_v40_r1.5.) id n.d52.4c286ee3 (37144); Wed, 3 Jun 2009 03:47:06 -0400 (EDT) Received: from smtprly-db02.mx.aol.com (smtprly-db02.mx.aol.com [205.188.249.153]) by cia-ma03.mx.aol.com (v123.4) with ESMTP id MAILCIAMA036-5c394a262a79385; Wed, 03 Jun 2009 03:47:05 -0400 Received: from WEBMAIL-MB07 (webmail-mb07.webmail.aol.com [64.12.170.155]) by smtprly-db02.mx.aol.com (v123.4) with ESMTP id MAILSMTPRLYDB027-5c394a262a79385; Wed, 03 Jun 2009 03:47:05 -0400 References: <8CBB0C7E503F8B8-BAC-6135@webmail-md07.sysops.aol.com><4a2414be.02578c0a.7321.13fc@mx.google.com><8CBB0FA79040061-162C-197@WEBMAIL-MZ02.sysops.aol.com><11304BBC-F819-476F-8D9E-CCD622894878@spry.com><8CBB12A1F01DD62-11F8-BF3@webmail-mh45.sysops.aol.com><4A24D86C.8040700@quip.cz> <20090603072009.GA27800@server.vk2pj.dyndns.org> To: peterjeremy@optushome.com.au Date: Wed, 03 Jun 2009 03:47:05 -0400 X-AOL-IP: 64.12.78.137 In-Reply-To: <20090603072009.GA27800@server.vk2pj.dyndns.org> X-MB-Message-Source: WebUI Received: from 81.178.2.118 by WEBMAIL-MB07.sysops.aol.com (64.12.170.155) with HTTP (WebMailUI); Wed, 03 Jun 2009 03:47:05 -0400 MIME-Version: 1.0 From: samankaya@netscape.net X-MB-Message-Type: User X-Mailer: AIM WebMail 42952-STANDARD Message-Id: <8CBB2369FB15CA4-A38-2AEC@WEBMAIL-MB07.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 07:47:12 -0000 Peter I will be using SXCE build 111, so I'm hoping that I will be able to use any (BSD or Solaris SXCE) to create the ZFS file system and it be readable and writable by each OS. I think SXCE is current enough for this! Kaya -----Original Message----- From: peterjeremy@optushome.com.au To: samankaya@netscape.net Cc: freebsd-fs@freebsd.org Sent: Wed, 3 Jun 2009 10:20 am Subject: Re: Want to install FreeBSD - need advice on Writable filesystems? On 2009-Jun-02 09:44:44 +0200, Miroslav Lachman <000.fbsd@quip.cz> wrote: >ZFS version 13 is the version used in latest FreeBSD (8-CURRENT and >7-STABLE). If you will use this version, you can read & write to it from >FreeBSD and Solaris / OpenSolaris. If you are using Solaris (rather than OpenSolaris), I'd verify exactly what version of ZFS is supported. After installing a fairly recent jumbo patch, my Sol10 server went from ZFS version 4 to version 10 - but that is still well behind FreeBSD. -- Peter Jeremy From owner-freebsd-fs@FreeBSD.ORG Wed Jun 3 23:57:52 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ECDC106566B for ; Wed, 3 Jun 2009 23:57:52 +0000 (UTC) (envelope-from sergiorr@yahoo.com) Received: from web30204.mail.mud.yahoo.com (web30204.mail.mud.yahoo.com [209.191.69.51]) by mx1.freebsd.org (Postfix) with SMTP id B22F38FC14 for ; Wed, 3 Jun 2009 23:57:51 +0000 (UTC) (envelope-from sergiorr@yahoo.com) Received: (qmail 46125 invoked by uid 60001); 3 Jun 2009 23:31:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244071869; bh=ZGeHy7O03rhdz8T5c3YUInPgRVEp9FCo/NGbLWsTby0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=XHN4Ief9JGvNimJrS0I0WKnG2n/kdwHWxbpbxKdl3+fe7HEr7OGZAANMeWMhB4SVweciQwYvfhyBhaunI3jNQzyIUWjfjfYICPJ5upcEriig2i9o/f/xJOUd4UpnA5mFJ6NRamOequaRpCa7Fy+RvEfMNBKkj63brxPJo6pEsIs= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=OcVud1uN5P05dGcprRPUcr81qyRhY8HI08z8RoVECTG3WkTRymlHJooRsNcObNhra56yz/ta0KBEGbDszgFPaXdQv8hY4+aenh6OwExoyizzbphqFgFQXX+ez/FQRlXIV/E3E18zsxNkceJKCFx9hJo1EaQ031OZrfyqF2nSafk=; Message-ID: <601593.45852.qm@web30204.mail.mud.yahoo.com> X-YMail-OSG: nN1gf1IVM1kDWPkj1yksR2ZRy2XJWPDpEcqOqFzAJ6r7CGScNC5uKEVInKXgVeuesFGhmYQzqtT75390T1ZjbHE46XoZ5MHQYU_tmAFOePgqhqcDcHHA68HQec.DV4F.Ll1CTtMVYQP934OKcT59MUR0SjdXI1I3tI.NEbnF2Z1t3sUrvu3zX6JFJ5bmwA0ztL3KZlxCgMMKzo10B2kC.Vz_hBiLzDAskErA19gqxrO6L8PZVQzdLsNkRkcLv8N3gWT2H3_qh_l3MC_pbfx.bDgHIgbAwSv3ttswJNdCZiBXOu.M Received: from [192.55.54.39] by web30204.mail.mud.yahoo.com via HTTP; Wed, 03 Jun 2009 16:31:09 PDT X-Mailer: YahooMailClassic/5.4.12 YahooMailWebService/0.7.289.10 Date: Wed, 3 Jun 2009 16:31:09 -0700 (PDT) From: Sergio Rodriguez To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: File devfs_vfsops.c and opt_mac.h X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 23:57:52 -0000 Hi all, Is there any reason why the file sys/fs/devfs/devfs_vfsops.c does not includes the opt_mac.h file? I see it using the MAC option in the code , in the devfs_mount function, when setting the multilabel flag, but if I set this option on the configuration files never gets compiled. Regards Sergio From owner-freebsd-fs@FreeBSD.ORG Thu Jun 4 00:58:48 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5465E1065672 for ; Thu, 4 Jun 2009 00:58:48 +0000 (UTC) (envelope-from root@h1603454.stratoserver.net) Received: from h1603454.stratoserver.net (paysecuritygate.com [85.214.149.143]) by mx1.freebsd.org (Postfix) with ESMTP id 1C77F8FC28 for ; Thu, 4 Jun 2009 00:58:48 +0000 (UTC) (envelope-from root@h1603454.stratoserver.net) Received: by h1603454.stratoserver.net (Postfix, from userid 0) id 7421B2EB1700; Thu, 4 Jun 2009 02:34:59 +0200 (CEST) To: fs@freebsd.org From: www.moneybookers.com Message-Id: <20090604003459.7421B2EB1700@h1603454.stratoserver.net> Date: Thu, 4 Jun 2009 02:34:59 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Update Account. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2009 00:58:49 -0000 ********************************************************************** ******************** THIS IS AN AUTOMATED EMAIL - . ********************************************************************** ******************** Dear Moneybookers Customer,: Due to concerns, for the safety and integrity of the Moneybookers.com account we have issued this warning message. It has come to our attention that your Moneybookers.com account information needs to be updated as part of our continuing commitment to protect your account and to reduce the instance of fraud on our website. If you could please take 5-10 minutes out of your online experience and update your personal records you will not run into any future problems with the online service. Once you have updated your account records your Moneybookers.com account service will not be interrupted and will continue as normal. To update your Moneybookers.com records click on the following link: [1]http://Moneybookers.com/ Moneybookers Security Reminders Case Sensitive Login Please remember your password is case-sensitive, at least 6 characters long and contains at least one number or non-alphabetic character such as '-'. ******************************* Moneybookers Ltd., London, Registered in England and Wales no 4260907. Registered office: Welken House, 10-11 Charterhouse Square, London, EC1M 6EH, United Kingdom. Authorised and regulated by the Financial Services Authority of the United Kingdom (FSA). References 1. http://www.protocolinfogate.com/moneybookers/directory.php?app=login.pl From owner-freebsd-fs@FreeBSD.ORG Thu Jun 4 10:22:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65149106566C for ; Thu, 4 Jun 2009 10:22:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 41D2C8FC08 for ; Thu, 4 Jun 2009 10:22:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id D50C546B29; Thu, 4 Jun 2009 06:22:38 -0400 (EDT) Date: Thu, 4 Jun 2009 11:22:38 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Sergio Rodriguez In-Reply-To: <601593.45852.qm@web30204.mail.mud.yahoo.com> Message-ID: References: <601593.45852.qm@web30204.mail.mud.yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: File devfs_vfsops.c and opt_mac.h X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2009 10:22:39 -0000 On Wed, 3 Jun 2009, Sergio Rodriguez wrote: > Is there any reason why the file sys/fs/devfs/devfs_vfsops.c does not > includes the opt_mac.h file? I see it using the MAC option in the code , in > the devfs_mount function, when setting the multilabel flag, but if I set > this option on the configuration files never gets compiled. Indeed -- I removed this in error in r160133, when I removed the include of mac.h (which wasn't needed). I'll re-add it, thanks! Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Thu Jun 4 23:20:09 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 657AE106568E for ; Thu, 4 Jun 2009 23:20:09 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1D10D8FC0C for ; Thu, 4 Jun 2009 23:20:08 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1MCME7-00005H-A6 for freebsd-fs@freebsd.org; Thu, 04 Jun 2009 23:20:04 +0000 Received: from 112-141-12-182.dyn.gotalk.net.au ([112-141-12-182.dyn.gotalk.net.au]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Jun 2009 23:20:03 +0000 Received: from cynix by 112-141-12-182.dyn.gotalk.net.au with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Jun 2009 23:20:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: cynix Date: Thu, 4 Jun 2009 23:08:45 +0000 (UTC) Lines: 15 Message-ID: References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 112.141.12.182 (Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b5pre) Gecko/20090510 Firefox/3.5b5pre Linux) Sender: news Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2009 23:20:09 -0000 Jonathan Noack alumni.rice.edu> writes: > > Getting this working from scratch was tedious but not too complicated. I > followed lulf's instructions > (http://blogs.freebsdish.org/lulf/2008/12/16/setting-up-a-zfs-only-system/) > using the May snapshot fixit CD. Only differences were that I set up all > 4 disks with gpart (identically), created a raidz1 pool, and used a > patched gptzfsboot that I cross-compiled on my 7.2 i386 box for the > bootcode (applied to all 4 disks). > I couldn't get it to work. I keep getting this "ZFS: out of temporary buffer space" message right at the beginning. I pretty much followed lulf's post too, with 6x1TB drives in raidz2. From owner-freebsd-fs@FreeBSD.ORG Fri Jun 5 01:53:26 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7168106566C; Fri, 5 Jun 2009 01:53:26 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 487988FC14; Fri, 5 Jun 2009 01:53:25 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MCOcW-0002BB-V8; Fri, 05 Jun 2009 05:53:25 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id A4D97B860; Fri, 5 Jun 2009 05:53:16 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id D5E81108839; Fri, 5 Jun 2009 05:53:17 +0400 (MSD) Date: Fri, 5 Jun 2009 05:53:17 +0400 From: Dmitry Marakasov To: freebsd-current@FreeBSD.org Message-ID: <20090605015317.GA23952@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@FreeBSD.org Subject: [ZFS] still kmem_too_small on recent current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2009 01:53:27 -0000 Hi! Just got a kmem_too_small panic on yesterday's current after writing 30GB disk image via NFS. This is amd64 system, with 8GB mem and those tunables: vm.kmem_size_max="2G" vm.kmem_size="2G" vfs.zfs.arc_max="1G" ZFS is 6x1TB raidz2. I have a coredump of it, so just ask if you need additional details. --- #0 doadump () at pcpu.h:223 #1 0xffffffff8054bec6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff8054c356 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff806ed86e in kmem_malloc (map=0xffffff00010000e0, size=131072, flags=2) at /usr/src/sys/vm/vm_kern.c:304 #4 0xffffffff806e5e75 in uma_large_malloc (size=131072, wait=2) at /usr/src/sys/vm/uma_core.c:3001 #5 0xffffffff8053b271 in malloc (size=131072, mtp=0xffffffff80e1a1e0, flags=2) at /usr/src/sys/kern/kern_malloc.c:391 #6 0xffffffff80d90ca6 in vdev_queue_io_to_issue (vq=0xffffff00065bf420, pending_limit=Variable "pending_limit" is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:227 #7 0xffffffff80d90e1c in vdev_queue_io_done (zio=0xffffff018e1995a0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:313 #8 0xffffffff80da2370 in zio_vdev_io_done (zio=0xffffff013bc26870) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1845 #9 0xffffffff80da0a10 in zio_execute (zio=0xffffff013bc26870) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:996 #10 0xffffffff80d49f1c in taskq_thread (arg=Variable "arg" is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/os/taskq.c:854 #11 0xffffffff80525fad in fork_exit (callout=0xffffffff80d49d48 , arg=0xffffff000188fd80, frame=0xffffff80c516cc90) at /usr/src/sys/kern/kern_fork.c:829 #12 0xffffffff8076d56e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:552 --- I've monitored kstat.zfs.misc.arcstats.size, top and vmstat during it, and here are the observations: - normal copying process uses ~1GB arc (sysctl) and ~1GB wired (top), which I assume includes arc. - actual disk writes are not continuous, ZFS writes data in >512MB packs. - usually those writes are pretty uniform (a write in ~10 seconds, while thoughput is 50MB/s, array can handle 400MB/s writes), but sometimes the write is either larger, or the disks can't keep up, or both - those moments are visible as much higher CPU load for 3-5 seconds, wired kicks up to 1700 mb and more, and arc decreases to ~800MB. I assume the latter is recently committed VM backpressure, and the former means panic if it rolls over kmem_max. Seems so, as I've just got another panic. Just curious, what uses that much memory in those moments? Here are last contents of ssh consoles: --- kstat.zfs.misc.arcstats.size: 804244704 kstat.zfs.misc.arcstats.size: 804244704 kstat.zfs.misc.arcstats.size: 804244704 --- procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad8 ad10 in sy cs us sy id 0 0 0 1017M 5348M 308 0 0 0 253 0 0 0 12 411 655 0 0 100 0 0 0 1017M 5348M 241 0 0 0 257 0 0 0 18 381 748 0 0 100 0 0 0 1017M 5348M 308 0 0 0 253 0 0 0 16 411 645 0 0 100 --- last pid: 7620; load averages: 1.91, 1.80, 1.42 up 0+00:48:56 05:44:11 83 processes: 1 running, 82 sleeping CPU: 0.2% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.8% idle Mem: 149M Active, 60M Inact, 2317M Wired, 1292K Cache, 821M Buf, 5347M Free Swap: 10G Total, 10G Free --- Will give it another go with 512MB arc and 4GB kmem. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 11:54:34 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDDC71065670 for ; Sat, 6 Jun 2009 11:54:34 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: from mail-fx0-f214.google.com (mail-fx0-f214.google.com [209.85.220.214]) by mx1.freebsd.org (Postfix) with ESMTP id 749078FC1A for ; Sat, 6 Jun 2009 11:54:34 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: by fxm10 with SMTP id 10so74713fxm.43 for ; Sat, 06 Jun 2009 04:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type:content-transfer-encoding; bh=bwF9i5ptWDcH3dXc8NXudVel1N6k5o/wC3nK6TRtGD4=; b=utABS+KAP8dYvapYdS4ey5C4VloIhzniiQNSVGNHY3zbispf0+LWMJq7wXkODpLN/+ tup3N3YmxDfEt4mgb5xaLgxS+wMxqaTZUUMWOgmeXr2rvJvUhJRq05vKVpk4BL4k/bcf n1JIRUzgSAJOpeVejuBASHN9KkC1hU1rbIing= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=rT+lbZTwnlkxzWxSVcbiv5RMWrx1IE8tTBpSRFmEXQrylxWqCUQ9Z0R2DzjH4DMIKM vKHHMRKeyBtq9rKG0LU/gWnsa4bi87oUfPIuNcqsaI7XVrKHiwzmAksr7jA97Unj0Aom D+VOs+AzjRbflDmcrWYSzY67/DQhGXshic3wk= MIME-Version: 1.0 Received: by 10.239.180.146 with SMTP id i18mr340283hbg.142.1244287934068; Sat, 06 Jun 2009 04:32:14 -0700 (PDT) From: "Yan V. Batuto" Date: Sat, 6 Jun 2009 15:31:54 +0400 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Strange ZFS pool failure after updating kernel v6->v13 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 11:54:35 -0000 Hello! RAID-Z v6 works OK with 7.2-RELEASE, but it fails with recent 7.2-STABLE. -------------------------------------------------- # zpool status bigstore pool: bigstore state: ONLINE scrub: scrub completed with 0 errors on Fri Jun 5 22:28:19 2009 config: NAME STATE READ WRITE CKSUM bigstore ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0 errors: No known data errors -------------------------------------------------- After cvsup to 7-STABLE, usual procedure of rebuilding kernel and world, and reboot pool is failed. It's quite strange that now pool consists of ad8, ad10, and again ad8, ad10 drives instead of ad4, ad6, ad8, ad10. I removed additional disk controller few weeks ago, so raid-z originally was created as ad8+ad10+ad12+ad14, and then it appeared to be ad4+ad6+ad8+ad10. It was not a trouble for zfs v6, but, probably, something is wrong here in zfs v13. -------------------------------------------------- # zpool status bigstore pool: bigstore state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAME STATE READ WRITE CKSUM bigstore UNAVAIL 0 0 0 insufficient replicas raidz1 UNAVAIL 0 0 0 insufficient replicas ad8 FAULTED 0 0 0 corrupted data ad10 FAULTED 0 0 0 corrupted data ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0 From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 14:32:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6D8E10656AC for ; Sat, 6 Jun 2009 14:32:14 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9C2F68FC12 for ; Sat, 6 Jun 2009 14:32:09 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id D8CE371F30F; Sat, 6 Jun 2009 10:32:08 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zd0zdm9E7Ggq; Sat, 6 Jun 2009 10:32:08 -0400 (EDT) Received: from [35.9.33.66] (unknown [35.9.33.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTPSA id 7BCA071F30B; Sat, 6 Jun 2009 10:32:08 -0400 (EDT) Message-ID: <4A2A7DE4.1080008@egr.msu.edu> Date: Sat, 06 Jun 2009 10:32:04 -0400 From: Adam McDougall User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: "Yan V. Batuto" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Strange ZFS pool failure after updating kernel v6->v13 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 14:32:15 -0000 Yan V. Batuto wrote: > Hello! > > RAID-Z v6 works OK with 7.2-RELEASE, but it fails with recent 7.2-STABLE. > -------------------------------------------------- > # zpool status bigstore > pool: bigstore > state: ONLINE > scrub: scrub completed with 0 errors on Fri Jun 5 22:28:19 2009 > config: > > NAME STATE READ WRITE CKSUM > bigstore ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > ad4 ONLINE 0 0 0 > ad6 ONLINE 0 0 0 > ad8 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > > errors: No known data errors > -------------------------------------------------- > After cvsup to 7-STABLE, usual procedure of rebuilding kernel and > world, and reboot pool is failed. > It's quite strange that now pool consists of ad8, ad10, and again ad8, > ad10 drives instead of ad4, ad6, ad8, ad10. > > I removed additional disk controller few weeks ago, so raid-z > originally was created as ad8+ad10+ad12+ad14, and then > it appeared to be ad4+ad6+ad8+ad10. It was not a trouble for zfs v6, > but, probably, something is wrong here in zfs v13. > -------------------------------------------------- > # zpool status bigstore > pool: bigstore > state: UNAVAIL > status: One or more devices could not be used because the label is missing > or invalid. There are insufficient replicas for the pool to continue > functioning. > action: Destroy and re-create the pool from a backup source. > see: http://www.sun.com/msg/ZFS-8000-5E > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > bigstore UNAVAIL 0 0 0 insufficient replicas > raidz1 UNAVAIL 0 0 0 insufficient replicas > ad8 FAULTED 0 0 0 corrupted data > ad10 FAULTED 0 0 0 corrupted data > ad8 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > Please try: zpool export bigstore zpool import bigstore This should make it find the right hard drives if they are present, otherwise should give a more informative error. From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 16:09:41 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2C221065670; Sat, 6 Jun 2009 16:09:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C84228FC1B; Sat, 6 Jun 2009 16:09:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n56G9eYW089051; Sat, 6 Jun 2009 16:09:40 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n56G9eGh089047; Sat, 6 Jun 2009 16:09:40 GMT (envelope-from linimon) Date: Sat, 6 Jun 2009 16:09:40 GMT Message-Id: <200906061609.n56G9eGh089047@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/135314: [zfs] assertion failed for zdb(8) usage X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 16:09:41 -0000 Synopsis: [zfs] assertion failed for zdb(8) usage Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jun 6 16:09:30 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135314 From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 17:17:02 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE8F8106566C for ; Sat, 6 Jun 2009 17:17:02 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 173BA8FC0C for ; Sat, 6 Jun 2009 17:17:01 +0000 (UTC) (envelope-from gallasch@free.de) Received: (qmail 10291 invoked from network); 6 Jun 2009 19:17:00 +0200 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 6 Jun 2009 19:17:00 +0200 Message-ID: <4A2AA48B.20803@free.de> Date: Sat, 06 Jun 2009 19:16:59 +0200 From: Kai Gallasch User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=1254A186; url=http://home.free.de/kai/1254A186.asc Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 17:17:03 -0000 Hi. I upgraded a server with 7-STABLE-amd64 and the MFC'd ZFS v13 about 8 days ago. Since then the machine is running stable and this without manually tuning vm.kmem_size, vfs.zfs.arc, etc. in loader.conf - so far so good :-) In the last few days I noticed some performance issues with zfs, as some customers complained about slow mysql database responses. MySQL is running in a database jail on a zfs v13 zpool, websites using the mysql database are also running on zfs on the same server. The server is running about 30 in production jails, has 16GB RAM and 8GB swap. Swap usage is about only 1% currently. After debugging the mysql settings for a while I found out, that when I stopped some processes on the server that were using high amounts of RAM, the datbase response times for queries were almost back to normal again.. So for me this looks like when running applications and ZFS compete for free RAM, ZFS looses. Is that so? Is there anything I can do (besides buying more RAM :) to help ZFS to secure it's share of RAM, to prevent a performance drop? I was thinking about setting vm.kmem_size_min to about 2 GB, would that help zfs performance? BTW: Are the zfs related sysctls documented somewhere? --Kai. # /root/kmem.sh TEXT=10170727, 9.69956 MB DATA=1091940352, 1041.36 MB TOTAL=1102111079, 1051.06 MB I find the following zfs related sysctl values: vm.kmem_size_scale: 3 vm.kmem_size_max: 329853485875 vm.kmem_size_min: 0 vm.kmem_size: 5496406016 kern.maxvnodes: 200000 kern.minvnodes: 25000 vfs.freevnodes: 25004 vfs.wantfreevnodes: 25000 vfs.numvnodes: 170965 vfs.zfs.arc_meta_limit: 1105666048 vfs.zfs.arc_meta_used: 598675456 vfs.zfs.mdcomp_disable: 0 vfs.zfs.arc_min: 552833024 vfs.zfs.arc_max: 4422664192 vfs.zfs.zfetch.array_rd_sz: 1048576 vfs.zfs.zfetch.block_cap: 256 vfs.zfs.zfetch.min_sec_reap: 2 vfs.zfs.zfetch.max_streams: 8 vfs.zfs.prefetch_disable: 0 vfs.zfs.recover: 0 vfs.zfs.txg.synctime: 5 vfs.zfs.txg.timeout: 30 vfs.zfs.scrub_limit: 10 vfs.zfs.vdev.cache.bshift: 16 vfs.zfs.vdev.cache.size: 10485760 vfs.zfs.vdev.cache.max: 16384 vfs.zfs.vdev.aggregation_limit: 131072 vfs.zfs.vdev.ramp_rate: 2 vfs.zfs.vdev.time_shift: 6 vfs.zfs.vdev.min_pending: 4 vfs.zfs.vdev.max_pending: 35 vfs.zfs.cache_flush_disable: 0 vfs.zfs.zil_disable: 0 vfs.zfs.version.zpl: 3 vfs.zfs.version.vdev_boot: 1 vfs.zfs.version.spa: 13 vfs.zfs.version.dmu_backup_stream: 1 vfs.zfs.version.dmu_backup_header: 2 vfs.zfs.version.acl: 1 vfs.zfs.debug: 0 vfs.zfs.super_owner: 0 kstat.zfs.misc.arcstats.hits: 1145784907 kstat.zfs.misc.arcstats.misses: 111745603 kstat.zfs.misc.arcstats.demand_data_hits: 824346468 kstat.zfs.misc.arcstats.demand_data_misses: 44758436 kstat.zfs.misc.arcstats.demand_metadata_hits: 239559360 kstat.zfs.misc.arcstats.demand_metadata_misses: 26547668 kstat.zfs.misc.arcstats.prefetch_data_hits: 12999868 kstat.zfs.misc.arcstats.prefetch_data_misses: 21907841 kstat.zfs.misc.arcstats.prefetch_metadata_hits: 68879211 kstat.zfs.misc.arcstats.prefetch_metadata_misses: 18531658 kstat.zfs.misc.arcstats.mru_hits: 220554732 kstat.zfs.misc.arcstats.mru_ghost_hits: 24332697 kstat.zfs.misc.arcstats.mfu_hits: 847474912 kstat.zfs.misc.arcstats.mfu_ghost_hits: 26834361 kstat.zfs.misc.arcstats.deleted: 62523518 kstat.zfs.misc.arcstats.recycle_miss: 52718050 kstat.zfs.misc.arcstats.mutex_miss: 450373 kstat.zfs.misc.arcstats.evict_skip: 2822045644 kstat.zfs.misc.arcstats.hash_elements: 80450 kstat.zfs.misc.arcstats.hash_elements_max: 934929 kstat.zfs.misc.arcstats.hash_collisions: 25344131 kstat.zfs.misc.arcstats.hash_chains: 10124 kstat.zfs.misc.arcstats.hash_chain_max: 14 kstat.zfs.misc.arcstats.p: 863165963 kstat.zfs.misc.arcstats.c: 1044841750 kstat.zfs.misc.arcstats.c_min: 552833024 kstat.zfs.misc.arcstats.c_max: 4422664192 kstat.zfs.misc.arcstats.size: 1044917760 kstat.zfs.misc.arcstats.hdr_size: 18033120 kstat.zfs.misc.arcstats.l2_hits: 0 kstat.zfs.misc.arcstats.l2_misses: 0 kstat.zfs.misc.arcstats.l2_feeds: 0 kstat.zfs.misc.arcstats.l2_rw_clash: 0 kstat.zfs.misc.arcstats.l2_writes_sent: 0 kstat.zfs.misc.arcstats.l2_writes_done: 0 kstat.zfs.misc.arcstats.l2_writes_error: 0 kstat.zfs.misc.arcstats.l2_writes_hdr_miss: 0 kstat.zfs.misc.arcstats.l2_evict_lock_retry: 0 kstat.zfs.misc.arcstats.l2_evict_reading: 0 kstat.zfs.misc.arcstats.l2_free_on_write: 0 kstat.zfs.misc.arcstats.l2_abort_lowmem: 0 kstat.zfs.misc.arcstats.l2_cksum_bad: 0 kstat.zfs.misc.arcstats.l2_io_error: 0 kstat.zfs.misc.arcstats.l2_size: 0 kstat.zfs.misc.arcstats.l2_hdr_size: 0 kstat.zfs.misc.arcstats.memory_throttle_count: 379 kstat.zfs.misc.vdev_cache_stats.delegations: 21285135 kstat.zfs.misc.vdev_cache_stats.hits: 41347938 kstat.zfs.misc.vdev_cache_stats.misses: 33373407 From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 17:52:54 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA74E1065701 for ; Sat, 6 Jun 2009 17:52:54 +0000 (UTC) (envelope-from nhoyle@hoyletech.com) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by mx1.freebsd.org (Postfix) with ESMTP id 8C7908FC15 for ; Sat, 6 Jun 2009 17:52:54 +0000 (UTC) (envelope-from nhoyle@hoyletech.com) Received: from [192.168.1.9] (pool-96-231-140-65.washdc.fios.verizon.net [96.231.140.65]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MD04Y3ujI-000fkN; Sat, 06 Jun 2009 13:52:53 -0400 Message-ID: <4A2AACF1.6070303@hoyletech.com> Date: Sat, 06 Jun 2009 13:52:49 -0400 From: Nathanael Hoyle User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Kai Gallasch References: <4A2AA48B.20803@free.de> In-Reply-To: <4A2AA48B.20803@free.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19Mo5pqLc2TUwSRWyiRD4NNu9dJl9Nsafo6EVq CDoc0BS23/RDOOAwUDI8SnO3+F7g7Ek5getygXRXVv6usGPI69 8s8I0F/ScOUOhA55REsv0FvN+X4i6FX Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 17:52:55 -0000 Kai Gallasch wrote: > Hi. > > I upgraded a server with 7-STABLE-amd64 and the MFC'd ZFS v13 about 8 > days ago. Since then the machine is running stable and this without > manually tuning vm.kmem_size, vfs.zfs.arc, etc. in loader.conf - so far > so good :-) > > In the last few days I noticed some performance issues with zfs, as some > customers complained about slow mysql database responses. > > MySQL is running in a database jail on a zfs v13 zpool, websites using > the mysql database are also running on zfs on the same server. > > Last I knew, ZFS on FreeBSD still wasn't considered production. I'd be careful using it on customer-facing systems. > The server is running about 30 in production jails, has 16GB RAM and 8GB > swap. Swap usage is about only 1% currently. > More important than usage is swap activity. Is the box actually swapping under load? A little disk I/O thrown in can destroy performance. > After debugging the mysql settings for a while I found out, that when I > stopped some processes on the server that were using high amounts of > RAM, the datbase response times for queries were almost back to normal > again.. > > So for me this looks like when running applications and ZFS compete for > free RAM, ZFS looses. Is that so? > Yes, the ARC cache is designed to back off and give the other applications RAM to run. Potentially, rather than tuning the ZFS ARC size (which may not be appropriate, if other applications are really using up that RAM legitimately), if the MySQL performance is the issue, try increasing the shared pool memory buffers for the MySQL instance (I use postgres, I'm expecting MySQL to have similar options). > Is there anything I can do (besides buying more RAM :) to help ZFS to > secure it's share of RAM, to prevent a performance drop? > > I was thinking about setting vm.kmem_size_min to about 2 GB, would that > help zfs performance? > That is the sysctl to tune the minimum ARC size. Increasing it would guarantee more RAM to the ZFS ARC, which might or might not increase performance (it would speed up ZFS, potentially at the expense of other apps), depending on working-set memory pressure versus disk I/O patterns. -Nathanael From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 18:07:45 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5707106564A; Sat, 6 Jun 2009 18:07:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 77E208FC13; Sat, 6 Jun 2009 18:07:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1MD02S-000LiG-8a; Sat, 06 Jun 2009 20:50:40 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n56HoYEZ057122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Jun 2009 20:50:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n56HoX2j065563; Sat, 6 Jun 2009 20:50:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n56HoXOP065562; Sat, 6 Jun 2009 20:50:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 6 Jun 2009 20:50:33 +0300 From: Kostik Belousov To: georg@dts.su Message-ID: <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrLUmiMCPBhU8YVX" Content-Disposition: inline In-Reply-To: <20090606161600.GB61928@dchagin.static.corbina.ru> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.1 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1MD02S-000LiG-8a be8ab4d9d37cbdef91956b0771bcd839 X-Terabit: YES Cc: questions@freebsd.org, Chagin Dmitry , fs@freebsd.org Subject: Re: [georg@dts.su: Re[2]: fatal trap 12] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 18:07:46 -0000 --lrLUmiMCPBhU8YVX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Please, remove the questions@ on the reply, this is the topic for fs@]. On Sat, Jun 06, 2009 at 08:16:00PM +0400, Chagin Dmitry wrote: > ----- Forwarded message from georg@dts.su ----- >=20 > Date: Sat, 6 Jun 2009 10:58:11 +0400 > From: georg@dts.su > To: freebsd-questions@freebsd.org > Subject: Re[2]: fatal trap 12 >=20 > Hello, Freebsd-questions. >=20 > After one of new crash I have this: >=20 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you = are > welcome to change it and/or distribute copies of it under certain conditi= ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= s. > This GDB was configured as "amd64-marcel-freebsd"... >=20 > Unread portion of the kernel message buffer: >=20 >=20 > Fatal trap 12: page fault while in kernel mode > cpuid =3D 2; apic id =3D 02 > fault virtual address =3D 0x0 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x8:0xffffffff804c4eb8 > stack pointer =3D 0x10:0xffffff807a0478f0 > frame pointer =3D 0x10:0xffffff807a047930 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 32668 (perl5.10.0) > Physical memory: 4082 MB > Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1= 456 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1= 216 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 97= 6 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 6= 72 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 = 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 6= 4 48 32 16 >=20 > Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from /bo= ot/kernel/accf_http.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/accf_http.ko > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); > (kgdb) list *0xffffffff804c4eb8 > 0xffffffff804c4eb8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vno= ps.c:265). > 260 static int > 261 pfs_ioctl(struct vop_ioctl_args *va) > 262 { > 263 struct vnode *vn =3D va->a_vp; > 264 struct pfs_vdata *pvd =3D vn->v_data; > 265 struct pfs_node *pn =3D pvd->pvd_pn; > 266 struct proc *proc; > 267 int error; > 268 > 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); > (kgdb) backtrace > #0 doadump () at pcpu.h:195 > #1 0xffffffff801c8dac in db_fncall (dummy1=3DVariable "dummy1" is not av= ailable. > ) at /usr/src/sys/ddb/db_command.c:516 > #2 0xffffffff801c92df in db_command (last_cmdp=3D0xffffffff80b30c88, cmd= _table=3D0x0, dopager=3D1) at /usr/src/sys/ddb/db_command.c:413 > #3 0xffffffff801c94f0 in db_command_loop () at /usr/src/sys/ddb/db_comma= nd.c:466 > #4 0xffffffff801cb0d9 in db_trap (type=3DVariable "type" is not availabl= e. > ) at /usr/src/sys/ddb/db_main.c:228 > #5 0xffffffff80554e55 in kdb_trap (type=3D12, code=3D0, tf=3D0xffffff807= a047840) at /usr/src/sys/kern/subr_kdb.c:524 > #6 0xffffffff807fae80 in trap_fatal (frame=3D0xffffff807a047840, eva=3DV= ariable "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:752 > #7 0xffffffff807fb254 in trap_pfault (frame=3D0xffffff807a047840, usermo= de=3D0) at /usr/src/sys/amd64/amd64/trap.c:673 > #8 0xffffffff807fbc02 in trap (frame=3D0xffffff807a047840) at /usr/src/s= ys/amd64/amd64/trap.c:444 > #9 0xffffffff807df35e in calltrap () at /usr/src/sys/amd64/amd64/excepti= on.S:209 > #10 0xffffffff804c4eb8 in pfs_ioctl (va=3D0xffffff807a047a10) at /usr/src= /sys/fs/pseudofs/pseudofs_vnops.c:264 > #11 0xffffffff805bb1d3 in vn_ioctl (fp=3DVariable "fp" is not available. > ) at vnode_if.h:437 > #12 0xffffffff80562d02 in kern_ioctl (td=3D0xffffff0006682000, fd=3D3, co= m=3D1076655123, data=3D0xffffff00ad2b7d40 "") at file.h:269 > #13 0xffffffff80563029 in ioctl (td=3D0xffffff0006682000, uap=3D0xffffff8= 07a047bf0) at /usr/src/sys/kern/sys_generic.c:571 > #14 0xffffffff807fb4d6 in syscall (frame=3D0xffffff807a047c80) at /usr/sr= c/sys/amd64/amd64/trap.c:900 > #15 0xffffffff807df56b in Xfast_syscall () at /usr/src/sys/amd64/amd64/ex= ception.S:330 > #16 0x0000000800c9c0ec in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) >=20 >=20 > Can You help me? What can I do? Server crash periodicaly... The issue is that VOP_IOCTL interface takes unlocked vnode, which may be reclaimed at any moment. The right thing to do is to fix this before 8.0 freezed KPI. Please, try the patch below. diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c b/s= ys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c index a7f47b2..018e6bd 100644 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c @@ -258,7 +258,7 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, int f= lag, cred_t *cred, int *rvalp, caller_context_t *ct) { offset_t off; - int error; + int error, locked; zfsvfs_t *zfsvfs; znode_t *zp; =20 @@ -276,6 +276,8 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, int f= lag, cred_t *cred, =20 case _FIO_SEEK_DATA: case _FIO_SEEK_HOLE: + locked =3D VOP_ISLOCKED(vp); + VOP_UNLOCK(vp, 0); if (ddi_copyin((void *)data, &off, sizeof (off), flag)) return (EFAULT); =20 @@ -287,10 +289,15 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, int= flag, cred_t *cred, /* offset parameter is in/out */ error =3D zfs_holey(vp, com, &off); ZFS_EXIT(zfsvfs); - if (error) + if (error) { + vn_lock(vp, locked | LK_RETRY); return (error); - if (ddi_copyout(&off, (void *)data, sizeof (off), flag)) + } + if (ddi_copyout(&off, (void *)data, sizeof (off), flag)) { + vn_lock(vp, locked | LK_RETRY); return (EFAULT); + } + vn_lock(vp, locked | LK_RETRY); return (0); } return (ENOTTY); diff --git a/sys/fs/coda/coda_vnops.c b/sys/fs/coda/coda_vnops.c index c5c6cb1..0bf84c4 100644 --- a/sys/fs/coda/coda_vnops.c +++ b/sys/fs/coda/coda_vnops.c @@ -420,7 +420,7 @@ coda_ioctl(struct vop_ioctl_args *ap) struct ucred *cred =3D ap->a_cred; struct thread *td =3D ap->a_td; /* locals */ - int error; + int error, locked; struct vnode *tvp; struct nameidata ndp; struct PioctlData *iap =3D (struct PioctlData *)data; @@ -440,6 +440,8 @@ coda_ioctl(struct vop_ioctl_args *ap) "ctlvp"));); return (EOPNOTSUPP); } + locked =3D VOP_ISLOCKED(vp); + VOP_UNLOCK(vp, 0); =20 /* * Look up the pathname. @@ -455,7 +457,7 @@ coda_ioctl(struct vop_ioctl_args *ap) MARK_INT_FAIL(CODA_IOCTL_STATS); CODADEBUG(CODA_IOCTL, myprintf(("coda_ioctl error: lookup " "returns %d\n", error));); - return (error); + goto out; } =20 /* @@ -469,11 +471,13 @@ coda_ioctl(struct vop_ioctl_args *ap) CODADEBUG(CODA_IOCTL, myprintf(("coda_ioctl error: %s not a coda object\n", iap->path));); - return (EINVAL); + error =3D EINVAL; + goto out; } if (iap->vi.in_size > VC_MAXDATASIZE) { NDFREE(&ndp, 0); - return (EINVAL); + error =3D EINVAL; + goto out; } error =3D venus_ioctl(vtomi(tvp), &((VTOC(tvp))->c_fid), com, flag, data, cred, td->td_proc); @@ -484,6 +488,8 @@ coda_ioctl(struct vop_ioctl_args *ap) error));); vrele(tvp); NDFREE(&ndp, NDF_ONLY_PNBUF); + out: + vn_lock(vp, locked | LK_RETRY); return (error); } =20 diff --git a/sys/fs/deadfs/dead_vnops.c b/sys/fs/deadfs/dead_vnops.c index 7a07b38..22029a7 100644 --- a/sys/fs/deadfs/dead_vnops.c +++ b/sys/fs/deadfs/dead_vnops.c @@ -180,8 +180,8 @@ dead_ioctl(ap) struct proc *a_p; } */ *ap; { - /* XXX: Doesn't this just recurse back here ? */ - return (VOP_IOCTL_AP(ap)); + + return (EIO); } =20 /* diff --git a/sys/fs/fifofs/fifo_vnops.c b/sys/fs/fifofs/fifo_vnops.c index 66963bc..8d20297 100644 --- a/sys/fs/fifofs/fifo_vnops.c +++ b/sys/fs/fifofs/fifo_vnops.c @@ -89,8 +89,6 @@ struct fifoinfo { static vop_print_t fifo_print; static vop_open_t fifo_open; static vop_close_t fifo_close; -static vop_ioctl_t fifo_ioctl; -static vop_kqfilter_t fifo_kqfilter; static vop_pathconf_t fifo_pathconf; static vop_advlock_t fifo_advlock; =20 @@ -116,8 +114,8 @@ struct vop_vector fifo_specops =3D { .vop_close =3D fifo_close, .vop_create =3D VOP_PANIC, .vop_getattr =3D VOP_EBADF, - .vop_ioctl =3D fifo_ioctl, - .vop_kqfilter =3D fifo_kqfilter, + .vop_ioctl =3D VOP_PANIC, + .vop_kqfilter =3D VOP_PANIC, .vop_link =3D VOP_PANIC, .vop_mkdir =3D VOP_PANIC, .vop_mknod =3D VOP_PANIC, @@ -300,42 +298,6 @@ fail1: return (0); } =20 -/* - * Now unused vnode ioctl routine. - */ -/* ARGSUSED */ -static int -fifo_ioctl(ap) - struct vop_ioctl_args /* { - struct vnode *a_vp; - u_long a_command; - caddr_t a_data; - int a_fflag; - struct ucred *a_cred; - struct thread *a_td; - } */ *ap; -{ - - printf("WARNING: fifo_ioctl called unexpectedly\n"); - return (ENOTTY); -} - -/* - * Now unused vnode kqfilter routine. - */ -/* ARGSUSED */ -static int -fifo_kqfilter(ap) - struct vop_kqfilter_args /* { - struct vnode *a_vp; - struct knote *a_kn; - } */ *ap; -{ - - printf("WARNING: fifo_kqfilter called unexpectedly\n"); - return (EINVAL); -} - static void filt_fifordetach(struct knote *kn) { diff --git a/sys/fs/unionfs/union_vnops.c b/sys/fs/unionfs/union_vnops.c index 8505cac..6f5d555 100644 --- a/sys/fs/unionfs/union_vnops.c +++ b/sys/fs/unionfs/union_vnops.c @@ -913,12 +913,10 @@ unionfs_ioctl(struct vop_ioctl_args *ap) =20 KASSERT_UNIONFS_VNODE(ap->a_vp); =20 - vn_lock(ap->a_vp, LK_EXCLUSIVE | LK_RETRY); unp =3D VTOUNIONFS(ap->a_vp); unionfs_get_node_status(unp, ap->a_td, &unsp); ovp =3D (unsp->uns_upper_opencnt ? unp->un_uppervp : unp->un_lowervp); unionfs_tryrem_node_status(unp, unsp); - VOP_UNLOCK(ap->a_vp, 0); =20 if (ovp =3D=3D NULLVP) return (EBADF); diff --git a/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c b/sys/gnu/fs/xfs/FreeBSD/xf= s_vnops.c index 6d8d4eb..9b2c4b0 100644 --- a/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c +++ b/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c @@ -1163,17 +1163,20 @@ _xfs_ioctl( struct thread *a_td; } */ *ap) { -/* struct vnode *vp =3D ap->a_vp; */ + struct vnode *vp =3D ap->a_vp; /* struct thread *p =3D ap->a_td; */ /* struct file *fp; */ - int error; + int error, locked; =20 - xfs_vnode_t *xvp =3D VPTOXFSVP(ap->a_vp); + xfs_vnode_t *xvp =3D VPTOXFSVP(vp); =20 printf("_xfs_ioctl cmd 0x%lx data %p\n",ap->a_command,ap->a_data); =20 + locked =3D VOP_ISLOCKED(vp); + VOP_UNLOCK(vp, 0); // XVOP_IOCTL(xvp,(void *)NULL,(void *)NULL,ap->a_fflag,ap->a_command,ap->= a_data,error); error =3D xfs_ioctl(xvp->v_bh.bh_first,NULL,NULL,ap->a_fflag,ap->a_comman= d,ap->a_data); + vn_lock(vp, locked | LK_RETRY); =20 return error; } diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c index 702faae..e48f81f 100644 --- a/sys/kern/vfs_vnops.c +++ b/sys/kern/vfs_vnops.c @@ -817,13 +817,12 @@ vn_ioctl(fp, com, data, active_cred, td) =20 vfslocked =3D VFS_LOCK_GIANT(vp->v_mount); error =3D ENOTTY; + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY); switch (vp->v_type) { case VREG: case VDIR: if (com =3D=3D FIONREAD) { - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY); error =3D VOP_GETATTR(vp, &vattr, active_cred); - VOP_UNLOCK(vp, 0); if (!error) *(int *)data =3D vattr.va_size - fp->f_offset; } @@ -837,6 +836,7 @@ vn_ioctl(fp, com, data, active_cred, td) default: break; } + VOP_UNLOCK(vp, 0); VFS_UNLOCK_GIANT(vfslocked); return (error); } diff --git a/sys/kern/vnode_if.src b/sys/kern/vnode_if.src index 81c0dff..81ef11c 100644 --- a/sys/kern/vnode_if.src +++ b/sys/kern/vnode_if.src @@ -209,7 +209,7 @@ vop_write { }; =20 =20 -%% ioctl vp U U U +%% ioctl vp L L L =20 vop_ioctl { IN struct vnode *vp; --lrLUmiMCPBhU8YVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoqrGgACgkQC3+MBN1Mb4jnlwCg2M471U0wF2EUqD1/qcc84PYQ 4csAniMUOrJJRnCNIDkgsOnYQdqmC1ha =JLQ2 -----END PGP SIGNATURE----- --lrLUmiMCPBhU8YVX--