From owner-freebsd-fs@FreeBSD.ORG Mon Jul 16 03:15:04 2012 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 73CE3106564A; Mon, 16 Jul 2012 03:15:04 +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 4044F8FC0C; Mon, 16 Jul 2012 03:15:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6G3F4cr017254; Mon, 16 Jul 2012 03:15:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6G3F4Sa017250; Mon, 16 Jul 2012 03:15:04 GMT (envelope-from linimon) Date: Mon, 16 Jul 2012 03:15:04 GMT Message-Id: <201207160315.q6G3F4Sa017250@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/169813: [zfs] [patch] Update with Illumos gate issues: 1796, 2871, 2903, 2957 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, 16 Jul 2012 03:15:04 -0000 Old Synopsis: [zfs] Update with Illumos gate issues: 1796, 2871, 2903, 2957 New Synopsis: [zfs] [patch] Update with Illumos gate issues: 1796, 2871, 2903, 2957 Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 16 03:14:51 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=169813 From owner-freebsd-fs@FreeBSD.ORG Mon Jul 16 11:08:53 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8773E1065673 for ; Mon, 16 Jul 2012 11:08:53 +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 70F978FC1A for ; Mon, 16 Jul 2012 11:08:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6GB8rba093969 for ; Mon, 16 Jul 2012 11:08:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6GB8prL093966 for freebsd-fs@FreeBSD.org; Mon, 16 Jul 2012 11:08:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jul 2012 11:08:51 GMT Message-Id: <201207161108.q6GB8prL093966@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, 16 Jul 2012 11:08: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/169813 fs [zfs] [patch] Update with Illumos gate issues: 1796, 2 o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167066 fs [zfs] ZVOLs not appearing in /dev/zvol o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b 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 o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab 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/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file 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/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero 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 o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount 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 conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using 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 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 bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o 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 s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' 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 o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl 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 bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits 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 bin/70600 fs fsck(8) throws files away when it can't grow lost+foun 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/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 281 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jul 16 14:40:21 2012 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 6AE05106566B for ; Mon, 16 Jul 2012 14:40:21 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 412258FC0A for ; Mon, 16 Jul 2012 14:40:21 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10966372pbb.13 for ; Mon, 16 Jul 2012 07:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=REVZ08kqeeXmyvfqLch4Tdqj540mYcO8Y+JwnHXKFnA=; b=qLiRgeAdQbD/a9Qi8eJyT/zlLa4mjQL3qWSA84Eg0ObhDjGaK09jNWvnnrcFdK7Y3i jjg96ohAE1CCA+j8b6m1mcSZ6cbtsUaiNNQcLix8fOgiTbBjixSzZa31l1SfTaKcA+MC LoJwHzqxK5Y7g6yeROYBdx8ToCv+tX3u3RiWgscnLUEsS+NxdY8pOTMrDPzg6URrk+mn E+tFvGpf7+amt8ElU7s9P1ZwO9To8TIwmZCQMemsQMSmZC6QGMymGshzra8t7FAh4d5H ld4sV1nk/RWkzJX8YBb6qPGoW6u6BRGQuu9oBZuBLQDwbSvp9PSYATalJOufohfYH5jb fg1g== MIME-Version: 1.0 Received: by 10.68.130.67 with SMTP id oc3mr27506107pbb.18.1342449620939; Mon, 16 Jul 2012 07:40:20 -0700 (PDT) Received: by 10.66.17.202 with HTTP; Mon, 16 Jul 2012 07:40:20 -0700 (PDT) Date: Mon, 16 Jul 2012 16:40:20 +0200 Message-ID: From: claudiu vasadi To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: "zfs receive -F" not destroying snapshots that do not exist on the sending side 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, 16 Jul 2012 14:40:21 -0000 Hello list, Ono our backup machine, I noticed that the old snapshots do not get deleted. I checked the script that sends snapshots there and it is using the "-F" flag for "zfs receive" which, according to the man page, should delete snapshots that do not exist on the sending side. In my case, it does not. The machines in question are 9-STABLE (around r236943) exhibiting no problems what so ever. I tried on other machines and got the same result. I did a quick test: zfs create rpool/test zfs snapshot rpool/test@snap1 zfs snapshot rpool/test@snap2 zfs snapshot rpool/test@snap3 zfs snapshot rpool/test@snap4 zfs send rpool/test@snap1 | ssh -c arcfour ssh backup.local zfs receive -F backup/test zfs send -i snap1 rpool/test@snap2 | ssh -c arcfour ssh backup.local zfs receive -F backup/test zfs send -i snap2 rpool/test@snap3 | ssh -c arcfour ssh backup.local zfs receive -F backup/test zfs destroy rpool/test@snap1 zfs send -i snap3 rpool/test@snap4 | ssh -c arcfour ssh backup.local zfs receive -F backup/test I think, snap1 should be deleted at this stage, but it is not. I also tried sending the initial snapshot with the "-R" flag but the results were the same. Is this expected behavior or some bug ? -- Best regards, Claudiu Vasadi From owner-freebsd-fs@FreeBSD.ORG Tue Jul 17 22:26:41 2012 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 8CC10106566C for ; Tue, 17 Jul 2012 22:26:41 +0000 (UTC) (envelope-from freebsd-fs@ch.pkts.ca) Received: from foster.nce.ubc.ca (cl-937.chi-02.us.sixxs.net [IPv6:2001:4978:f:3a8::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE328FC0C for ; Tue, 17 Jul 2012 22:26:41 +0000 (UTC) Received: from fedora14-x86-64.shechinah.mi.microbiology.ubc.ca ([137.82.128.93]) (authenticated bits=0) by foster.nce.ubc.ca (8.14.4/8.14.4) with ESMTP id q6HMQTp4010201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 17 Jul 2012 15:26:30 -0700 Date: Tue, 17 Jul 2012 15:26:29 -0700 From: CH To: freebsd-fs@freebsd.org Message-ID: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, DATE_IN_FUTURE_12_24,SARE_SUB_OBFU_OTHER autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on foster.nce.ubc.ca Subject: Can you list internal checksums of a ZFS filesystem? 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, 17 Jul 2012 22:26:41 -0000 Hello list, I'm moving data to a ZFS filesystem, and it's a ton of big files (more than 3 terabytes). I don't trust the network copy command completely, and so I'd like to compare checksums. I'm not looking forward to it, since it's going to be a slow process, especially if I can't run the command on the server. Since ZFS already has computed and stored checksums for every file on the destination machine, is there an easy way to extract that from the filesystem? Perhaps 'ls -lR --checksums' or similar? Note, checksums still have to be calculated on the source machine, and so the overall operation will still take the same length of time (assuming ZFS is faster than HFS+), but it does save a lot of cpu and disk reads on the destination machine, which can then be used for other things. Thanks! -- CH From owner-freebsd-fs@FreeBSD.ORG Tue Jul 17 22:54:59 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54FA01065673 for ; Tue, 17 Jul 2012 22:54:59 +0000 (UTC) (envelope-from prvs=154567bda3=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id DA1878FC0C for ; Tue, 17 Jul 2012 22:54:58 +0000 (UTC) X-Spam-Processed: mail1.multiplay.co.uk, Tue, 17 Jul 2012 23:54:36 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50020823185.msg for ; Tue, 17 Jul 2012 23:54:35 +0100 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=154567bda3=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <451BA6FA76214F37B2F271F91708E275@multiplay.co.uk> From: "Steven Hartland" To: "CH" , References: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> Date: Tue, 17 Jul 2012 23:54:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: Subject: Re: Can you list internal checksums of a ZFS filesystem? 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, 17 Jul 2012 22:54:59 -0000 ----- Original Message ----- From: "CH" To: Sent: Tuesday, July 17, 2012 11:26 PM Subject: Can you list internal checksums of a ZFS filesystem? > Hello list, > > I'm moving data to a ZFS filesystem, and it's a ton of big files (more > than 3 terabytes). I don't trust the network copy command completely, > and so I'd like to compare checksums. I'm not looking forward to it, > since it's going to be a slow process, especially if I can't run the > command on the server. > > Since ZFS already has computed and stored checksums for every file on > the destination machine, is there an easy way to extract that from the > filesystem? Perhaps 'ls -lR --checksums' or similar? > > Note, checksums still have to be calculated on the source machine, and > so the overall operation will still take the same length of time > (assuming ZFS is faster than HFS+), but it does save a lot of cpu and > disk reads on the destination machine, which can then be used for other > things. IIRC its block level checksums, not file level ones so don't think this will be what your looking for. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Tue Jul 17 23:41:19 2012 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 B5617106566C for ; Tue, 17 Jul 2012 23:41:19 +0000 (UTC) (envelope-from jusher71@yahoo.com) Received: from nm33-vm5.bullet.mail.ne1.yahoo.com (nm33-vm5.bullet.mail.ne1.yahoo.com [98.138.229.69]) by mx1.freebsd.org (Postfix) with SMTP id 466358FC17 for ; Tue, 17 Jul 2012 23:41:19 +0000 (UTC) Received: from [98.138.90.57] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 17 Jul 2012 23:41:13 -0000 Received: from [98.138.89.194] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 17 Jul 2012 23:41:13 -0000 Received: from [127.0.0.1] by omp1052.mail.ne1.yahoo.com with NNFMP; 17 Jul 2012 23:41:13 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 498680.27195.bm@omp1052.mail.ne1.yahoo.com Received: (qmail 96392 invoked by uid 60001); 17 Jul 2012 23:41:13 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1342568473; bh=NB3DSyUvUwG6px6Hvc7slLv6/8Yvpzq0fAzTnvg8twc=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=O4E64PIaYxCgksUHm2ThxzDqB+9j792H1dYTz3kWKIFb+K7xEShQj+VP/0t6UvprI12dJVxfnCdZkq4VGeKFAQY2eVzKbW6QqAWc9ybliyrO/rQr4p3GEqEjY5elbMvM5fqHpusEsr/yDdGkIkvMunVTio1I/BZZUs9zkwl6+PU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=A7XONIYwuoD6IZuiO6RmWWQEX5UfomYUSE1qaxHlJ2GYAhvLspjeazDuB9627UlIYo7qn8ETorPk1RdGGDWzeA04q04aJBciBKPz58IkiWiosPV8msZ4l4SJ/+xeQd0ANVidjsCqLmKWjpwfJZEWa5/B/3ToqO1uTHELI7LMVfQ=; X-YMail-OSG: d8lUaFgVM1mNelFtNfCmNWglhZw6TrvS7l_ctzmlpEME.Hs 5gNuHnWm83BBVPa_p_lK0Lm1kLdjiP3SJ3Wb8cXHjd2kadF3qlchmbjjQM6T Gt8w7ccx5rFARP.uq0QW8bAoha_cYEcPyUX_pxP2Knkhun6bdBjejmy9Vkoi _gSGokf1PcDcdOfNrL5cpT325h.gy5qRTmdM7sUxxvGF04CnTUELMaNhsW2c v26nxOw5y3MKa85xsWZ4P1NJv_b6UHTAtJcDUvp2wnrjDnNgsVMJNG5S_JRG zwtzYNHuS3JAajwT6K62LNAEpzeu3ttj8oilVOEF1MHDbk_8cSjPbtvaeEWw 8hSU.wBtsI_PHTqn5D.UV6wFkU4BrhSGYaWpUiq7ZknuiOuDnaiYQa1IdtGJ ItQ-- Received: from [173.164.238.34] by web122506.mail.ne1.yahoo.com via HTTP; Tue, 17 Jul 2012 16:41:13 PDT X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.120.356233 Message-ID: <1342568473.95824.YahooMailClassic@web122506.mail.ne1.yahoo.com> Date: Tue, 17 Jul 2012 16:41:13 -0700 (PDT) From: Jason Usher To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Random LSI 9211 / mps issues... 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, 17 Jul 2012 23:41:19 -0000 Hello, I am happy to see that LSI is actually maintaining and publishing a driver for the 9211-8i card (the mps driver). If you use 8.3-RELEASE, the driver you receive is: mps0: Firmware: 07.00.00.00, Driver: 13.00.00.00-fbsd But I see that there is a newer 13.x driver on their website. However, they only provide a kernel module - which means I would need to remove mps which is nicely compiled into my kernel, and run a module instead. is there any way to get the newest mps driver code into my kernel, or do I need to revert to a module ? ----- I also wonder about any kind of drive blink functionality ... support at LSI has conceded that this is either missing or broken - they seemed to think it was a bug in the current driver, but I don't see that it is a function at all. Is anyone here blinking disks in any way with mps based cards ? We really like to have some kind of positive ID on disks when we remove them, etc. If the disk fails completely and the LED is off, I guess that's easy, but if it's still running, a solid LED is indistinguishable from an extremely busy disk, which also looks solid. Any thoughts ? Thanks. From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 05:08:03 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D9CD106564A for ; Wed, 18 Jul 2012 05:08:03 +0000 (UTC) (envelope-from freebsd-fs@ch.pkts.ca) Received: from foster.nce.ubc.ca (cl-937.chi-02.us.sixxs.net [IPv6:2001:4978:f:3a8::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2F71D8FC16 for ; Wed, 18 Jul 2012 05:08:03 +0000 (UTC) Received: from kirk.lan (S010600032d00065e.vc.shawcable.net [24.86.111.248]) (authenticated bits=0) by foster.nce.ubc.ca (8.14.4/8.14.4) with ESMTP id q6I57pqD012711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Jul 2012 22:07:52 -0700 Date: Tue, 17 Jul 2012 22:07:50 -0700 From: "CH" To: "Steven Hartland" Message-ID: <20120717220750.03a7b7c5@kirk.lan> In-Reply-To: <451BA6FA76214F37B2F271F91708E275@multiplay.co.uk> References: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> <451BA6FA76214F37B2F271F91708E275@multiplay.co.uk> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, DATE_IN_FUTURE_12_24,SARE_SUB_OBFU_OTHER autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on foster.nce.ubc.ca Cc: freebsd-fs@freebsd.org Subject: Re: Can you list internal checksums of a ZFS filesystem? 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, 18 Jul 2012 05:08:03 -0000 On Tue, 17 Jul 2012 23:54:38 +0100 "Steven Hartland" wrote: > ----- Original Message ----- > From: "CH" > To: > Sent: Tuesday, July 17, 2012 11:26 PM > Subject: Can you list internal checksums of a ZFS filesystem? > > > > Hello list, > > > > I'm moving data to a ZFS filesystem, and it's a ton of big files > > (more than 3 terabytes). I don't trust the network copy command > > completely, and so I'd like to compare checksums. I'm not looking > > forward to it, since it's going to be a slow process, especially if > > I can't run the command on the server. > > > > Since ZFS already has computed and stored checksums for every file > > on the destination machine, is there an easy way to extract that > > from the filesystem? Perhaps 'ls -lR --checksums' or similar? > > > > Note, checksums still have to be calculated on the source machine, > > and so the overall operation will still take the same length of time > > (assuming ZFS is faster than HFS+), but it does save a lot of cpu > > and disk reads on the destination machine, which can then be used > > for other things. > > IIRC it's block level checksums, not file level ones, so I don't think > this will be what you're looking for. > > Regards > Steve You're right, block-level checksums would be less efficient, and there probably isn't a handy program out there for generating the same block-level checksums on a non-ZFS system. I suspect it wouldn't (shouldn't?) be hard: for each file, while not eof, read block, checksum block, print checksum, repeat, compare list of checksums, do next file. As long as the checksum algorithm and the block size are the same, the thing should work. In any case, if the checksums are effectively unreachable from userspace, then I should just recalculate file-level checksums. Thanks CH From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 06:50:40 2012 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 735D01065670 for ; Wed, 18 Jul 2012 06:50:40 +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 D6C8F8FC0A for ; Wed, 18 Jul 2012 06:50:39 +0000 (UTC) Received: (qmail 24825 invoked from network); 18 Jul 2012 08:43:57 +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 AES128-SHA encrypted SMTP for ; 18 Jul 2012 08:43:57 +0200 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Kai Gallasch In-Reply-To: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> Date: Wed, 18 Jul 2012 08:43:57 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <6D778EEA-5B8F-4F59-B198-E5B098F3AE2C@free.de> References: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> To: CH X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org Subject: Re: Can you list internal checksums of a ZFS filesystem? 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, 18 Jul 2012 06:50:40 -0000 Am 18.07.2012 um 00:26 schrieb CH: >=20 > Hello list, >=20 > I'm moving data to a ZFS filesystem, and it's a ton of big files (more > than 3 terabytes). I don't trust the network copy command completely, > and so I'd like to compare checksums. I'm not looking forward to it, > since it's going to be a slow process, especially if I can't run the > command on the server.=20 You could use rsync for transfering the data. According to its man page rsync calculates checksums for transfered = files and on its initial run compares checksums on the sending and = receiving side for each file: = http://www.freebsd.org/cgi/man.cgi?query=3Drsync&apropos=3D0&sektion=3D0&m= anpath=3DFreeBSD+Ports&arch=3Ddefault&format=3Dhtml -c, --checksum This changes the way rsync checks if the files have been = changed and are in need of a transfer. Without this option, rsync = uses a "quick check" that (by default) checks if each file's = size and time of last modification match between the sender and = receiver. This option changes this to compare a 128-bit checksum = for each file that has a matching size. Generating the checksums = means that both sides will expend a lot of disk I/O reading = all the data in the files in the transfer (and this is prior = to any reading that will be done to transfer changed files), = so this can slow things down significantly. The sending side generates its checksums while it is = doing the file-system scan that builds the list of the available = files. The receiver generates its checksums when it is = scanning for changed files, and will checksum any file that has the = same size as the corresponding sender's file: files with either a = changed size or a changed checksum are selected for transfer. Note that rsync always verifies that each transferred = file was correctly reconstructed on the receiving side by = checking a whole-file checksum that is generated as the file is = trans- ferred, but that automatic after-the-transfer = verification has nothing to do with this option's before-the-transfer = "Does this file need to be updated?" check. For protocol 30 and beyond (first supported in = 3.0.0), the checksum used is MD5. For older protocols, the checksum = used is MD4. So at the first run starting rsync without -c switch and on a second = run with -c should be quite sufficient for making sure, data has not = changed after being transfered. (Except of course, the underlying = filesystem layers lie about this to the application or a wrongly = implemented MD5 in rsync :-) Also rsync makes it possible to transfer the data in severeal runs, at = times most convenient to you (or your network). It also supports a switch for limiting bandwith usage.. Have a nice day, Kai.= From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 07:26:36 2012 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 2E12B10657CD; Wed, 18 Jul 2012 07:26:36 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from violet.upc.es (violet.upc.es [147.83.2.51]) by mx1.freebsd.org (Postfix) with ESMTP id 973AA8FC0C; Wed, 18 Jul 2012 07:26:35 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by violet.upc.es (8.14.1/8.13.1) with ESMTP id q6I5t7Zj016423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 18 Jul 2012 07:55:07 +0200 Received: from portgus.lan (labtel2.upc.edu [147.83.40.20]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id q6I5t6sW012969 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Jul 2012 07:55:07 +0200 Message-ID: <50064FB2.3020409@entel.upc.edu> Date: Wed, 18 Jul 2012 07:54:58 +0200 From: =?UTF-8?B?R3VzdGF1IFDDqXJleiBpIFF1ZXJvbA==?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120620 Thunderbird/13.0.1 MIME-Version: 1.0 To: attilio@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (violet.upc.es [147.83.2.51]); Wed, 18 Jul 2012 07:55:07 +0200 (CEST) Cc: FreeBSD FS , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 18 Jul 2012 07:26:36 -0000 Sorry fo the delay. About the ntfs support, I'd go with fuse and leave the most relevant filesystems in kernel space. In fact filesystems not particulary specific and not tied our kernel would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the list is incomplete and I don't really know if all of them are yet implemenent in userspace) in my opinion. That would make them easier to maintain (changes in the kernel would only affect fuse, once fixed all the userspace filesystem would work again). As a bonus, we would get many working fs based on fuse. In the server side gluster is a desirable thing; in the desktop things like gvfs (in the linux world gvfs is used not only by gnome but also by kde or xfce) or truecrypt > > I'm fixing low hanging fruit for the moment (see r238411 for example) > and I still have to make a throughful review. > However my idea is to commit the support once: > - ntfs-3g is well stress-tested and proves to be bug-free > - there is no major/big technical issue pending after the reviews > > I'm now looking for people sticking with the branch and trying to > stress-test ntfs-3g as much as they can. For example I know that > Gustau (cc'ed) already had issues. It would be good if he tries to > reproduce them and make a full report. I've seen ntfs-3g+fuse crashing a few times and IIRC most of the time the problem happened while unmounting the filesystem. I don't have the core dump files at hand, so I'll try to fix gnn patches to compile with my recent current (it doesn't compile, time ago I fixed fuse but I guess those patches wouldn't be enough right now) and try to panic the machine. When I do I'll do full reports of the panics. > As final note, George as agreed to maintain FUSE in the long-term and > of course I'll give him an hand as time permits. Any moment you need help needed coding, testing, etc let me know. > Thanks, > Attilio > > -- --------------------------------------------------------------------------- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Departament d'Enginyeria Telemàtica O O O Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 08:45:46 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75D7C106566B; Wed, 18 Jul 2012 08:45:46 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 890068FC0A; Wed, 18 Jul 2012 08:45:45 +0000 (UTC) Received: by lbon10 with SMTP id n10so2281155lbo.13 for ; Wed, 18 Jul 2012 01:45:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gByP6bujPg5+G7evt+MkrvEIb63v3PVktMefwcDSPu0=; b=K2AjYUHEbgSdNhMtqhKmfrJTjabdRiO2cpa4vsD4dNYBH6JP+e/2y554SANLqEivo/ 1+t6tA8TGoT31GVcik4i+VBHhNK6U9Sy5gl311Uy7pvLr0CfbahLryZgCKhCWnZ5nfcU C2XjfvLzJ5xjf6e3aVumrkudPBYXCOou4ye/Lj1ox/OYpMNvsdhgZDWxc8kZ3MN6SUiJ NLGY6T96/mfTq2u5ohmNhU3wKiwXTYQ0WQZ1SCXTEsXLfy9N65vzkTNP1vhEpIprVlCl 1FpufisLy8BtMz7w5sQKwSCdAng7Py8EC5otn3AYJtiOevIcGDzsnNUVgAMjWoMc1VI7 7lfQ== MIME-Version: 1.0 Received: by 10.152.136.18 with SMTP id pw18mr2448260lab.17.1342601144207; Wed, 18 Jul 2012 01:45:44 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.27.65 with HTTP; Wed, 18 Jul 2012 01:45:44 -0700 (PDT) In-Reply-To: <50064FB2.3020409@entel.upc.edu> References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 18 Jul 2012 09:45:44 +0100 X-Google-Sender-Auth: 7y7dtpHbUdzgxxgtFzAUyMgYPdM Message-ID: From: Attilio Rao To: =?UTF-8?Q?Gustau_P=C3=A9rez_i_Querol?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD FS , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2012 08:45:46 -0000 2012/7/18, Gustau P=C3=A9rez i Querol : > > Sorry fo the delay. > > About the ntfs support, I'd go with fuse and leave the most relevant > filesystems in kernel space. In fact filesystems not particulary > specific and not tied our kernel would go to userspace; thinks like > smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the > list is incomplete and I don't really know if all of them are yet > implemenent in userspace) in my opinion. That would make them easier to > maintain (changes in the kernel would only affect fuse, once fixed all > the userspace filesystem would work again). > > As a bonus, we would get many working fs based on fuse. In the > server side gluster is a desirable thing; in the desktop things like > gvfs (in the linux world gvfs is used not only by gnome but also by kde > or xfce) or truecrypt I'm really concerned also about ntfs and smbfs at the moment. It seems that there is also a FUSE smbfs port, but I never used it and I'm not sure about its state at all. >> >> I'm fixing low hanging fruit for the moment (see r238411 for example) >> and I still have to make a throughful review. >> However my idea is to commit the support once: >> - ntfs-3g is well stress-tested and proves to be bug-free >> - there is no major/big technical issue pending after the reviews >> >> I'm now looking for people sticking with the branch and trying to >> stress-test ntfs-3g as much as they can. For example I know that >> Gustau (cc'ed) already had issues. It would be good if he tries to >> reproduce them and make a full report. > > I've seen ntfs-3g+fuse crashing a few times and IIRC most of the > time the problem happened while unmounting the filesystem. The FUSE module you had testing still has several bugs. You can try this patch: http://people.freebsd.org/~attilio/fuse_AW_DONE_ISDOTDOT_collision.patch on top of the FUSE branch I'm working on: svn://svn.freebsd.org/base/projects/fuse/ however it still doesn't address the cloning races (I'm rewriting it in order to take advantage of devfs_*_devpriv() interface right now). Thanks, Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 09:03:47 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id D4CCF106566C; Wed, 18 Jul 2012 09:03:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 3A8AE1515DB; Wed, 18 Jul 2012 09:03:47 +0000 (UTC) Message-ID: <50067BF2.40907@FreeBSD.org> Date: Wed, 18 Jul 2012 02:03:46 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= References: <50064FB2.3020409@entel.upc.edu> In-Reply-To: <50064FB2.3020409@entel.upc.edu> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: attilio@freebsd.org, FreeBSD FS , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 18 Jul 2012 09:03:47 -0000 On 07/17/2012 22:54, Gustau Pérez i Querol wrote: > In fact filesystems not particulary specific and not tied our kernel > would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for > example should be in userspace A big -1 here. The more native FS support we have the better off we are in terms of both people migrating from other OS', and people who need to maintain compatibility with other OS'. Personally I use both msdosfs and ext2fs extensively for the latter purpose, and would not want to see either removed. Doug -- Change is hard. From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 12:00:02 2012 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 B5D17106564A for ; Wed, 18 Jul 2012 12:00:02 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFCE8FC08 for ; Wed, 18 Jul 2012 12:00:02 +0000 (UTC) Received: by yhfs35 with SMTP id s35so1737353yhf.13 for ; Wed, 18 Jul 2012 05:00:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=EIiJzi2pqNm44nR15rLjHiSoeA54ZnyPZEillcyoHLg=; b=lQ+Qd1hbW7rb/MLxeNjbxQDby0wVS1p6h8zMxGicbXb0CYIOnEuRb4dBzu9/bEHfCu uANjDGZkmxHQlLuR0qIlJxFp1coMTKYBvZJWh3Q0vGxDBSIltOs0YA/jAAkxwe/QB4nn ZgAL6dIlCLDCsPZtbha65rpyfHLP+r1/Y61EWfea2TYfXz1d2k/O/FJs8reoXJec342F 3tKsZ4OO3Ck03ap/W40g2lOecAZ7eP/HidFqdJZdlP3wL9NbnKo08adxvxrdchCQXwdW 1wj2dk0I1s9gmTuBAY/Vx8ZNBDRfstLy/QV4yIFu90KUZtvCPeIMwacBovEhSNOyhJIN Ec0A== Received: by 10.236.193.105 with SMTP id j69mr513783yhn.21.1342612801723; Wed, 18 Jul 2012 05:00:01 -0700 (PDT) Received: from AL-MB-MWS0001.mediacomcorp.com (173-17-217-144.client.mchsi.com. [173.17.217.144]) by mx.google.com with ESMTPS id x7sm19419208ang.7.2012.07.18.04.59.58 (version=SSLv3 cipher=OTHER); Wed, 18 Jul 2012 04:59:59 -0700 (PDT) Date: Wed, 18 Jul 2012 06:59:57 -0500 From: Chuck Burns To: freebsd-fs@freebsd.org Message-Id: <20120718065957.d1c7f91a.break19@gmail.com> In-Reply-To: <50067BF2.40907@FreeBSD.org> References: <50064FB2.3020409@entel.upc.edu> <50067BF2.40907@FreeBSD.org> X-Mailer: Sylpheed 3.1.3 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 18 Jul 2012 12:00:02 -0000 On Wed, 18 Jul 2012 02:03:46 -0700 Doug Barton wrote: > On 07/17/2012 22:54, Gustau P=E9rez i Querol wrote: > > In fact filesystems not particulary specific and not tied our kernel > > would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for > > example should be in userspace >=20 > A big -1 here. >=20 > The more native FS support we have the better off we are in terms of > both people migrating from other OS', and people who need to maintain > compatibility with other OS'. Personally I use both msdosfs and ext2fs > extensively for the latter purpose, and would not want to see either > removed. Agree with Doug. Fuse is generally much slower than native access, and has= higher CPU cost as well. My poor athlonxp 2k+ jumps to 100% CPU usage whe= n I copy files from either an ext4fuse or ntfs-3g filesystem to UFS. Pleas= e do not remove native access, and I would like to see even more native sup= port. --=20 Chuck Burns From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 12:10:04 2012 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 16C381065673 for ; Wed, 18 Jul 2012 12:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EBC9D8FC17 for ; Wed, 18 Jul 2012 12:10:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6ICA38i031852 for ; Wed, 18 Jul 2012 12:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6ICA3HC031850; Wed, 18 Jul 2012 12:10:03 GMT (envelope-from gnats) Date: Wed, 18 Jul 2012 12:10:03 GMT Message-Id: <201207181210.q6ICA3HC031850@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andrey Simonenko Cc: Subject: Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly atomic updates X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Simonenko List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2012 12:10:04 -0000 The following reply was made to PR kern/136865; it has been noted by GNATS. From: Andrey Simonenko To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly atomic updates Date: Wed, 18 Jul 2012 15:08:40 +0300 List of important changes from nfse-20120310 to nfse-20120718. Command line options -2, -n and -r now are not supported by nfse. Added new command line option -m to nfse, that specifies whether nfse should service MOUNT protocol requests and what it should support from this protocol. Added new option -resvport to nfs.exports, that specifies whether NFS and NLM RPC requests should be received from sender's reserved IP port numbers (default, always and weakauth modes). Added new option -mnt_mount to nfs.exports, that specifies settings for MOUNT protocol's procedures MNT, UMNT and UMNTALL (default, regfile and resvport arguments). Tried to make the nfse compatible mode completely compatible with exports(5) configurations: http://nfse.sourceforge.net/COMPATIBILITY From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 12:15:55 2012 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 89293106566B; Wed, 18 Jul 2012 12:15:55 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id F02778FC12; Wed, 18 Jul 2012 12:15:54 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id q6IAPnw8002416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 18 Jul 2012 12:25:49 +0200 Received: from portgus.lan (labtel2.upc.edu [147.83.40.20]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id q6IAPnUi011345 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Jul 2012 12:25:49 +0200 Message-ID: <50068F24.3080208@entel.upc.edu> Date: Wed, 18 Jul 2012 12:25:40 +0200 From: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120620 Thunderbird/13.0.1 MIME-Version: 1.0 To: Doug Barton References: <50064FB2.3020409@entel.upc.edu> <50067BF2.40907@FreeBSD.org> In-Reply-To: <50067BF2.40907@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Wed, 18 Jul 2012 12:25:50 +0200 (CEST) Cc: FreeBSD FS , freebsd-current@FreeBSD.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 18 Jul 2012 12:15:55 -0000 > On 07/17/2012 22:54, Gustau Pérez i Querol wrote: >> In fact filesystems not particulary specific and not tied our kernel >> would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for >> example should be in userspace The list is incomplete and maybe wrong; maybe some should stay in the kernel. It was just a quick guess. If you are think the list should be reviewed, I completely agree. > A big -1 here. > > The more native FS support we have the better off we are in terms of > both people migrating from other OS', and people who need to maintain > compatibility with other OS'. Well, I don't think we would lose compatibility (but I may be wrong). I think there are some fs' too complex to implement or maintain, like the ntfs one. About the ntfs case there's a complete fs implementation of it in userspace. And there are also many other fs' implementations in userspace. I think we can benefit from those implementations, removing the burden of maintaining them in the kernel (it would have been useful to have it in userspace right now because of the vfs giant lock removal deadline). The fs' staying in the kernel should be well maintained, the others in userspace would always work too as long as fuse is up to date; if anything changes in the kernel only fuse would need to be fixed to allow the many fs' in userpace to work. In the final situation we would end having a few fs in the kernel (I don't exactly know which ones to keep) and then some in userspace that could be installed via ports. We wouldn't lose compatibility with other OS', I think instead we would have more compatibility because we could benefit from the implementation of many fs' in userspace. People migrating from other OS' would have the possibility of installing the appropriate fusefs port. Of course, I don't know the exact list of fs' staying and leaving. > Personally I use both msdosfs and ext2fs > extensively for the latter purpose, and would not want to see either > removed. Well, I don't know which ones I would remove/migrate to userspace. The msdosfs is probably one I wouldn't migrate. About the ext2 I used to use it time ago at work. Now I remember there was a GoC in 2009 to update the implementation and I would keep it in the kernel. We could even keep ext2 in the kernel and have support for it as a fusefs port; I could choose the kernel or the userspace implementation. At work I also have to deal with ext4 or exfat filesystems from time to time. Having a working fuse implementation would allow me to have a better compatibility with other OS'. -- --------------------------------------------------------------------------- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Departament d'Enginyeria Telemàtica O O O Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 14:59:00 2012 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 BB8E1106566C for ; Wed, 18 Jul 2012 14:59:00 +0000 (UTC) (envelope-from freebsd-fs@ch.pkts.ca) Received: from foster.nce.ubc.ca (cl-937.chi-02.us.sixxs.net [IPv6:2001:4978:f:3a8::2]) by mx1.freebsd.org (Postfix) with ESMTP id 463708FC1C for ; Wed, 18 Jul 2012 14:58:59 +0000 (UTC) Received: from kirk.lan (S010600032d00065e.vc.shawcable.net [24.86.111.248]) (authenticated bits=0) by foster.nce.ubc.ca (8.14.4/8.14.4) with ESMTP id q6IEvsUT023769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 18 Jul 2012 07:57:56 -0700 Date: Wed, 18 Jul 2012 07:57:54 -0700 From: CH To: Kai Gallasch Message-ID: <20120718075754.4908266b@kirk.lan> In-Reply-To: <6D778EEA-5B8F-4F59-B198-E5B098F3AE2C@free.de> References: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> <6D778EEA-5B8F-4F59-B198-E5B098F3AE2C@free.de> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_FUTURE_06_12,SARE_SUB_OBFU_OTHER autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on foster.nce.ubc.ca Cc: freebsd-fs@freebsd.org Subject: Re: Can you list internal checksums of a ZFS filesystem? 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, 18 Jul 2012 14:59:00 -0000 On Wed, 18 Jul 2012 08:43:57 +0200 Kai Gallasch wrote: > Am 18.07.2012 um 00:26 schrieb CH: > > > > Hello list, > > > > I'm moving data to a ZFS filesystem, and it's a ton of big files > > (more than 3 terabytes). I don't trust the network copy command > > completely, and so I'd like to compare checksums. I'm not looking > > forward to it, since it's going to be a slow process, especially if > > I can't run the command on the server. > > You could use rsync for transfering the data. > > According to its man page rsync calculates checksums for transfered > files and on its initial run compares checksums on the sending and > receiving side for each file: > > http://www.freebsd.org/cgi/man.cgi?query=rsync&apropos=0&sektion=0&manpath=FreeBSD+Ports&arch=default&format=html > > > So at the first run starting rsync without -c switch and on a > second run with -c should be quite sufficient for making sure, data > has not changed after being transfered. (Except of course, the > underlying filesystem layers lie about this to the application or a > wrongly implemented MD5 in rsync :-) > > Also rsync makes it possible to transfer the data in severeal runs, > at times most convenient to you (or your network). It also supports a > switch for limiting bandwith usage.. > > Have a nice day, > Kai. Actually, I did do rsync for the initial transfers, and it had to be restarted a couple of times for reasons that were not its fault (source computer rebooted, ssh connection lost, etc). However, after it finished copying everything (ie: exiting normally), I ran it again, and it found more stuff to copy. This shouldn't have happened since nothing was added to the source computer, and so now I distrust its results and want to check it independently. In particular, I don't trust its directory-walking algorithm, so some files may have been missed and may continue to be missed in future runs of rsync, with or without -c. The method I was going to use was 'find . -type f -print0 | xargs -0 md5sum > my.big.md5sum.file' on both source and destination, but if I can harvest the ZFS checksums (file or block) it would cut the cpu workload in half, and save a tree's worth of energy. From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 15:35:32 2012 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 44CB01065675 for ; Wed, 18 Jul 2012 15:35:32 +0000 (UTC) (envelope-from prvs=1546bf2d57=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id C6F0E8FC0A for ; Wed, 18 Jul 2012 15:35:31 +0000 (UTC) X-Spam-Processed: mail1.multiplay.co.uk, Wed, 18 Jul 2012 16:34:34 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50020834592.msg for ; Wed, 18 Jul 2012 16:34:34 +0100 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1546bf2d57=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <8A24A3EFF4314670BAED740A02373F27@multiplay.co.uk> From: "Steven Hartland" To: "CH" , "Kai Gallasch" References: <20120717152629.42e0641e@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca><6D778EEA-5B8F-4F59-B198-E5B098F3AE2C@free.de> <20120718075754.4908266b@kirk.lan> Date: Wed, 18 Jul 2012 16:34:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org Subject: Re: Can you list internal checksums of a ZFS filesystem? 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, 18 Jul 2012 15:35:32 -0000 ----- Original Message ----- From: "CH" > Actually, I did do rsync for the initial transfers, and it had to be > restarted a couple of times for reasons that were not its fault (source > computer rebooted, ssh connection lost, etc). However, after it > finished copying everything (ie: exiting normally), I ran it again, and > it found more stuff to copy. This shouldn't have happened since > nothing was added to the source computer, and so now I distrust its > results and want to check it independently. In particular, I don't > trust its directory-walking algorithm, so some files may have been > missed and may continue to be missed in future runs of rsync, with or > without -c. > > The method I was going to use was 'find . -type f -print0 | xargs -0 > md5sum > my.big.md5sum.file' on both source and destination, but if I > can harvest the ZFS checksums (file or block) it would cut the cpu > workload in half, and save a tree's worth of energy. rsync is reliable when run on run cleanly. If like you had interruptions and you where running using say -av then it can miss changes if files changed but size or timestamps didn't. I've never had an run complete cleanly with a re-run detecting new files where files weren't in fact added. As mentioned --checksum (-c) forces checksums to be compared on both ends which will allow you to verify all is good. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 16:40:11 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 499E6106564A for ; Wed, 18 Jul 2012 16:40:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 335638FC15 for ; Wed, 18 Jul 2012 16:40:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6IGe3dt068937 for ; Wed, 18 Jul 2012 16:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6IGe2we068936; Wed, 18 Jul 2012 16:40:02 GMT (envelope-from gnats) Date: Wed, 18 Jul 2012 16:40:02 GMT Message-Id: <201207181640.q6IGe2we068936@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Shane Ambler Cc: Subject: Re: kern/161968: [zfs] [hang] renaming snapshot with -r including a zvol snapshot causes total ZFS freeze/lockup X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Shane Ambler List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2012 16:40:11 -0000 The following reply was made to PR kern/161968; it has been noted by GNATS. From: Shane Ambler To: bug-followup@FreeBSD.org, peter.maloney@brockmann-consult.de Cc: Subject: Re: kern/161968: [zfs] [hang] renaming snapshot with -r including a zvol snapshot causes total ZFS freeze/lockup Date: Thu, 19 Jul 2012 01:59:46 +0930 I am running 9.0-RELEASE-p1 amd64 clang built world and get a hang with zfs rename -r. I find anything already running mostly keeps running (top started before the rename will hang) but any (uncached?) disk access will cause running progs to hang as well. No new progs can start not even a console login. I need to hard reset. Hardware is an ASUS P8H61-M LE/USB3 with corei5 and 8GB RAM using a WD10EARS-00Y5B1 (WD green 1TB SATA2). Partitioned with 1 64k boot partition and 1 zfs partition. Single disk zpool. The volume I have is allocated to swap. The commands I used for the volume are - zfs create -V 16G zrp/swap0 zfs set org.freebsd:swap=on zrp/swap0 zfs set copies=1 zrp/swap0 From a clean pool with no snapshots - zfs snapshot -r zrp@daily.01 -- works zfs rename -r zrp@daily.01 zrp@daily.02 -- hangs Alternatively - zfs snapshot -r zrp@daily.01 -- works zfs rename -r zrp/swap0@daily.01 zrp/swap0@daily.02 -- works zfs rename -r zrp@daily.01 zrp@daily.02 -- works zfs rename -r zrp@daily.02 zrp@daily.03 -- hangs - now renames vol From owner-freebsd-fs@FreeBSD.ORG Wed Jul 18 21:30:25 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D98B310656A7; Wed, 18 Jul 2012 21:30:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B83F8FC17; Wed, 18 Jul 2012 21:30:23 +0000 (UTC) Received: by weyx56 with SMTP id x56so1556586wey.13 for ; Wed, 18 Jul 2012 14:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=PCdscUIOIQ4JOeXRvI+Dcj4Fnho/E4C2wnNrArd9siw=; b=UlFnSHfNi2u+LbAqiSSUxxPEtAkdIG5hSw4tCYiZ0nrBrkG8ODpxJVBzNug9zjbiaf dVO5bUol87Cja3QvAmvZeZyvyA0t3ABazRsH/FRiTXuGhK4/R1y7OwgTzo3/1R/16Fvh kiOVtftxKe6UNbxeoRY1GlamNruVE0mTTRQOgvuJ+QK0cvL1pKNSIHgoSUE5JDtjDgY5 jbPCB8PwGFCJTZYDSsl6BuSw4D5pL5KJTThXJ7fABB+++mPOukUlEbaPQ8ceXgwgvDtB VKL++/ihzlkmB53CT/Njhzx39k/hoqIWSRazvUDwWrWWMdqQo2CY6+7nBehVpN3sm+H4 XESw== MIME-Version: 1.0 Received: by 10.180.100.136 with SMTP id ey8mr9941213wib.15.1342647022248; Wed, 18 Jul 2012 14:30:22 -0700 (PDT) Received: by 10.223.60.147 with HTTP; Wed, 18 Jul 2012 14:30:22 -0700 (PDT) In-Reply-To: <50064FB2.3020409@entel.upc.edu> References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 18 Jul 2012 14:30:22 -0700 Message-ID: From: Kevin Oberman To: =?UTF-8?Q?Gustau_P=C3=A9rez_i_Querol?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: attilio@freebsd.org, FreeBSD FS , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 18 Jul 2012 21:30:25 -0000 On Tue, Jul 17, 2012 at 10:54 PM, Gustau P=C3=A9rez i Querol wrote: > > Sorry fo the delay. > > About the ntfs support, I'd go with fuse and leave the most relevant > filesystems in kernel space. In fact filesystems not particulary specific > and not tied our kernel would go to userspace; thinks like smbfs, nwfs, > ntfs, ext2 o ext4 for example should be in userspace (the list is incompl= ete > and I don't really know if all of them are yet implemenent in userspace) = in > my opinion. That would make them easier to maintain (changes in the kerne= l > would only affect fuse, once fixed all the userspace filesystem would wor= k > again). > > As a bonus, we would get many working fs based on fuse. In the server > side gluster is a desirable thing; in the desktop things like gvfs (in th= e > linux world gvfs is used not only by gnome but also by kde or xfce) or > truecrypt > > >> >> I'm fixing low hanging fruit for the moment (see r238411 for example) >> and I still have to make a throughful review. >> However my idea is to commit the support once: >> - ntfs-3g is well stress-tested and proves to be bug-free >> - there is no major/big technical issue pending after the reviews >> >> I'm now looking for people sticking with the branch and trying to >> stress-test ntfs-3g as much as they can. For example I know that >> Gustau (cc'ed) already had issues. It would be good if he tries to >> reproduce them and make a full report. > > > I've seen ntfs-3g+fuse crashing a few times and IIRC most of the time = the > problem happened while unmounting the filesystem. I can reliably crash a system by doing an rsync to an ntfs-3g mounted FS. I have simply stopped doing it an have spent no time trying to track down the problem, but maybe anyone (gnn?) working on fusefs might want to try it. FWIW, I can to "rsync -avn local-path/ remote-system:ntfs-3g/path" always works. Remove the 'n' and actually move the data and it dies. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-fs@FreeBSD.ORG Thu Jul 19 07:59:01 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF4831065781 for ; Thu, 19 Jul 2012 07:59:01 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp1.insight.synacor.com [208.47.185.23]) by mx1.freebsd.org (Postfix) with ESMTP id B48448FC21 for ; Thu, 19 Jul 2012 07:59:01 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=1.1 cv=cnnrplXNdTCGMX75Rfp+qZ4kRGPDgeWy4wsObDoE3iQ= c=1 sm=0 a=190A9ldbhagA:10 a=jLN7EqiLvroA:10 a=Iq6-h-MAVXSD1YdytLAA:9 a=Q/oqmR4JO1zR3vNQamCQeQ==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.insight.synacor.com header.from=mueller23@insightbb.com; sender-id=softfail Authentication-Results: smtp02.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Received-SPF: softfail (smtp02.insight.synacor.com: transitional domain insightbb.com does not designate 74.134.26.53 as permitted sender) Received: from [74.134.26.53] ([74.134.26.53:49672] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.2.40 r(29895/29896)) with ESMTP id 41/DE-05404-39DB7005; Thu, 19 Jul 2012 03:56:04 -0400 Date: Thu, 19 Jul 2012 03:56:03 -0400 Message-ID: <41.DE.05404.39DB7005@smtp02.insight.synacor.com> From: "Thomas Mueller" To: freebsd-current@freebsd.org Cc: attilio@freebsd.org, FreeBSD FS Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 19 Jul 2012 07:59:02 -0000 On 07/17/2012 22:54, Gustau Pérez i Querol wrote: > In fact filesystems not particulary specific and not tied our kernel > would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for > example should be in userspace Doug Barton responded: > A big -1 here. > The more native FS support we have the better off we are in terms of > both people migrating from other OS', and people who need to maintain > compatibility with other OS'. Personally I use both msdosfs and ext2fs > extensively for the latter purpose, and would not want to see either > removed. > Doug Doug, I agree! I too use msdosfs and ext2fs for communication with other OSes. I've posted messages in previous threads on this topic relating to lingua franca file system. Tom From owner-freebsd-fs@FreeBSD.ORG Thu Jul 19 09:04:09 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18831106564A for ; Thu, 19 Jul 2012 09:04:09 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id 911C48FC0C for ; Thu, 19 Jul 2012 09:04:08 +0000 (UTC) Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id q6J946JA022396; Thu, 19 Jul 2012 11:04:07 +0200 Received: from webmail.entel.upc.edu (www-entel.upc.es [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id C279B2CBD0E; Thu, 19 Jul 2012 11:04:01 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 19 Jul 2012 11:04:01 +0200 From: Gustau Perez Querol To: In-Reply-To: <20120718065957.d1c7f91a.break19@gmail.com> References: <50064FB2.3020409@entel.upc.edu> <50067BF2.40907@FreeBSD.org> <20120718065957.d1c7f91a.break19@gmail.com> Message-ID: X-Sender: gperez@entel.upc.edu User-Agent: RoundCube Webmail/0.5.1 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Thu, 19 Jul 2012 11:04:07 +0200 (CEST) Cc: freebsd-fs@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 19 Jul 2012 09:04:09 -0000 On Wed, 18 Jul 2012 06:59:57 -0500, Chuck Burns wrote: > On Wed, 18 Jul 2012 02:03:46 -0700 > Doug Barton wrote: > >> On 07/17/2012 22:54, Gustau Pérez i Querol wrote: >> > In fact filesystems not particulary specific and not tied our >> kernel >> > would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 >> for >> > example should be in userspace >> >> A big -1 here. >> >> The more native FS support we have the better off we are in terms of >> both people migrating from other OS', and people who need to >> maintain >> compatibility with other OS'. Personally I use both msdosfs and >> ext2fs >> extensively for the latter purpose, and would not want to see either >> removed. > > Agree with Doug. Fuse is generally much slower than native access, > and has higher CPU cost as well. My poor athlonxp 2k+ jumps to 100% > CPU usage when I copy files from either an ext4fuse or ntfs-3g > filesystem to UFS. Please do not remove native access, and I would > like to see even more native support. I agree CPU is a concern. As I said I'd vote for a list of native and well maintained fs' in the kernel plus the option of a well maintained fuse support for the other fs'. I don't know the exact list, it was just an exmample. For example, the lingua-franca problem would end up with a well maintained native fs. If no one volunteers, then at least there would be the option of the userspace implementation. Let it be ntfs, ext2 or anything else. I do prefer slower access than no access at all; e.g.: I don't have native RW acess with NTFS today, and we're going have no access to NTFS when the mpsafe vfs deadline arrives. At least this is my opinion. For fuse and cpu problems, it has many internal problem that probably raise the CPU usage. At least I've never seen that kind of figures with a linux machine using fuse. Best, Gustau From owner-freebsd-fs@FreeBSD.ORG Thu Jul 19 12:35:26 2012 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 7B1FB106564A; Thu, 19 Jul 2012 12:35:26 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id D8A9E8FC14; Thu, 19 Jul 2012 12:35:25 +0000 (UTC) Received: from park.js.berklix.net (p5DCBF636.dip.t-dialin.net [93.203.246.54]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id q6JCZI3k097768; Thu, 19 Jul 2012 12:35:20 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.14.3/8.14.3) with ESMTP id q6JCaxHa013760; Thu, 19 Jul 2012 14:37:08 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id q6JCaka3073457; Thu, 19 Jul 2012 14:36:51 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201207191236.q6JCaka3073457@fire.js.berklix.net> To: FreeBSD FS , freebsd-current@freebsd.org From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 18 Jul 2012 02:03:46 PDT." <50067BF2.40907@FreeBSD.org> Date: Thu, 19 Jul 2012 14:36:46 +0200 Sender: jhs@berklix.com Cc: attilio@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 19 Jul 2012 12:35:26 -0000 Doug Barton wrote: > On 07/17/2012 22:54, Gustau Pérez i Querol wrote: > > In fact filesystems not particulary specific and not tied our kernel > > would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for > > example should be in userspace > > A big -1 here. > > The more native FS support we have the better off we are in terms of > both people migrating from other OS', and people who need to maintain > compatibility with other OS'. Personally I use both msdosfs and ext2fs > extensively for the latter purpose, and would not want to see either > removed. It would be regretable if FreeBSD dropped integrated FS support, Many embedded devices that could use BSD, use Linux, eg TV recorder: http://www.humaxfoxsathdr.co.uk/ Ext2/ext4 internal & USB Ext2/4 + FAT32 external. TV recorder: http://www.dreambox800.co.uk FAT. GPS: http://www.tomtom.com/en_gb/search/?q=linux FAT32. Manufacturers are often clueless about BSD, & suprised how much more attractive the BSD (non FSF!) licence is, removing integrated FS support would increase change deterrent. PS Re ext2: I'm looking for an equivalent of mkfs_ext2, any suggestions ? Ports maybe ? `man newfs` gives No useful hints: -T Forget that, I checked the source, its a ref to /etc/disktab SEE ALSO (from 8.2) fdformat(1), geom(4), disktab(5), fs(5), bsdlabel(8), camcontrol(8), dump(8), dumpfs(8), fsck(8), gjournal(8), makefs(8), mount(8), tunefs(8), gvinum(8) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from Yahoo & Hotmail dumped @Berklix. http://berklix.org/yahoo/ From owner-freebsd-fs@FreeBSD.ORG Thu Jul 19 13:57:05 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B31E0106564A; Thu, 19 Jul 2012 13:57:05 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4371A8FC18; Thu, 19 Jul 2012 13:57:05 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.5/8.14.5) with ESMTP id q6JDukb0057010 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 19 Jul 2012 14:56:54 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <5008121D.7010503@unsane.co.uk> Date: Thu, 19 Jul 2012 14:56:45 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: "Julian H. Stacey" References: <201207191236.q6JCaka3073457@fire.js.berklix.net> In-Reply-To: <201207191236.q6JCaka3073457@fire.js.berklix.net> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD FS , attilio@freebsd.org, freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 19 Jul 2012 13:57:05 -0000 On 19/07/2012 13:36, Julian H. Stacey wrote: > PS Re ext2: > I'm looking for an equivalent of mkfs_ext2, any suggestions ? Ports maybe ? sounds like you want sysutils/e2fsprogs ext2/3/4 mkfs/fsck etc. I believe. From owner-freebsd-fs@FreeBSD.ORG Fri Jul 20 07:40:50 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBC06106564A for ; Fri, 20 Jul 2012 07:40:50 +0000 (UTC) (envelope-from db@nipsi.de) Received: from fop.bsdsystems.de (mx.bsdsystems.de [88.198.57.43]) by mx1.freebsd.org (Postfix) with ESMTP id 78B528FC12 for ; Fri, 20 Jul 2012 07:40:50 +0000 (UTC) Received: from [172.16.10.254] (d015138.adsl.hansenet.de [80.171.15.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by fop.bsdsystems.de (Postfix) with ESMTP id 359083027CB for ; Fri, 20 Jul 2012 09:40:43 +0200 (CEST) From: dennis berger Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Jul 2012 09:40:42 +0200 Message-Id: <7FE7A5F3-53FF-4508-A3D6-562E8FA9764D@nipsi.de> To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: ISCSI on zvols with two maschines. What needs to be done? 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, 20 Jul 2012 07:40:50 -0000 Hi folks, The following question often comes to me, when I speak to my customers. Is it possible to attach two systems to the same storage array using = shared SAS and use istgt + zfs to provide=20 a reliable ISCSI target. This could be active/passive or later = active/active. In case it's not possible, what needs to be done? The questions that came into my mind. Can I connect two freebsd to the storage and boot them up? Just that = both systems would see the physical devices.=20 Can I start ZFS on both systems without writing on it? I would like to = use just block devices for ISCSI. Is everything still consistent? Does starting ZFS up already writing some sort of meta data to the = physical devices?! Can I start istgt on both systems without actually using the istgt on = one system?! Then CARP would be enough, wouldn't it. Or in case of active/active extend istgt to communicate with the other = istgt to not hand out a device twice?=20 Best, -dennis From owner-freebsd-fs@FreeBSD.ORG Fri Jul 20 09:30:06 2012 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 D48A9106564A for ; Fri, 20 Jul 2012 09:30:06 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF7D8FC14 for ; Fri, 20 Jul 2012 09:30:06 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so3340418wgb.31 for ; Fri, 20 Jul 2012 02:30:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=VPJb9B2EvbMwGBrt9e5KRFxanZpAECSQh2oRj22Bcr4=; b=Eh2isqgQmLotvrfiJ+3vUSHpe3T1BtY/Bjlq15I5hwCuAkbfBauxEOaAihxfqRXewR T/l2V1r/zdmTvGH655d99zGIn6593ahRj4pgawijqyZLf8hp4fdgjxyMw52G9Vo+5nmL lfjlzeVLAQGpHnOH/zkYfzOYkuFXezVz8Y/MN2YZbD5idqU8K03WBKkDwuhRcRnSWfwz gfluuvVJklnd3UKuofO4g44gNP44z9eu1gENZ1JIL6B3LFpT23loPAyRIWbJSH9T7l53 /bQCgLI6sUCzGCRfECLtrUr5kLgR4SJ2cX9lQlQgtFtBLgsk3cmNnfICm7xORpeXu6vi QjWA== Received: by 10.216.192.85 with SMTP id h63mr3211957wen.7.1342776604454; Fri, 20 Jul 2012 02:30:04 -0700 (PDT) Received: from [192.168.50.111] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id v5sm3297349eel.6.2012.07.20.02.30.02 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 02:30:03 -0700 (PDT) Message-ID: <5009251B.5010404@gmail.com> Date: Fri, 20 Jul 2012 11:30:03 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: zpool get all core dumps when no pool is active 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, 20 Jul 2012 09:30:06 -0000 Hello all. On my test machine with FreeBSD Current from 14-07-2012 i lost my zpool due to a disconnected power supply. I noticed when i do a zpool get all on a pool that is not active, zpool core dumps. I do not know if it should do this, but an error message that there are no active pools would make it nicer. hast2 ~ # zpool status pool: testpool state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-3C scan: none requested config: NAME STATE READ WRITE CKSUM testpool UNAVAIL 0 0 0 mirror-0 UNAVAIL 0 0 0 10238773687773245204 UNAVAIL 0 0 0 was /dev/gpt/disk0 7739197258598802985 UNAVAIL 0 0 0 was /dev/gpt/disk1 hast2 ~ # zpool get all Assertion failed: (nvlist_lookup_nvlist(config, "feature_stats", &features) == 0), file /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_config.c, line 250. Abort trap: 6 (core dumped) It leaves a core file -rw------- 1 root wheel 8990720 Jul 20 12:20 zpool.core Also a zpool get all testpool coredumps. regards Johan Hendriks Neuteboom Automatisering From owner-freebsd-fs@FreeBSD.ORG Fri Jul 20 10:31:29 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9779F106566B for ; Fri, 20 Jul 2012 10:31:29 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4FA518FC08 for ; Fri, 20 Jul 2012 10:31:29 +0000 (UTC) Received: by yhfs35 with SMTP id s35so4484756yhf.13 for ; Fri, 20 Jul 2012 03:31:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1iX0f0BL/Ahv5dzBNi3wmMHLfH3H9AN6VH3RbQh16AQ=; b=mihbDO8SqWx01ttJyT7BQp188/RlrdXyU4R22RZgfMkSYOZvlAjn3tlqbOdNoGj76I A3pE6vqu3SZEzCM5jrv0OB8jywsBiAx2AYX2dATVs2RKBnWRpQOKFR5rpXSXwHo5gqjS GqIVPcBbQdQaDplVINfWBb9y9c1ppBnQvxhAFo6PgdUdyMyuzblnjUB88NLS/2V2qeou xsB0Mr1B5hm7YACmTqM0IW235ljx0hbRow0TbWYaH65UzSxDTV8WKZ20wbVFzIQ7QqWE s+weHCIBFMbS69OoiEWmvU46crV238IpMw+QRSoCfu80HALJVF5wjw4nZ3PqO7D0yV/B b7FQ== MIME-Version: 1.0 Received: by 10.60.8.8 with SMTP id n8mr6487022oea.38.1342780287811; Fri, 20 Jul 2012 03:31:27 -0700 (PDT) Received: by 10.76.71.42 with HTTP; Fri, 20 Jul 2012 03:31:27 -0700 (PDT) In-Reply-To: <5009251B.5010404@gmail.com> References: <5009251B.5010404@gmail.com> Date: Fri, 20 Jul 2012 18:31:27 +0800 Message-ID: From: Marcelo Araujo To: Johan Hendriks Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: zpool get all core dumps when no pool is active X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 10:31:29 -0000 Hello Johan, I think it is the normal behavior on CURRENT, due by default there is the INVARIANTS support that will perform run-time assertion checks and tests to verify the integrity of kernel. I made the same test in one machine here using 9.1-BETA1 without INVARIANTS and it does not happen with me. INVARIANTS: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html May you check if you have this option in your KERNEL? Or in case you are using the GENERIC, you must have it there. Best Regards, - Araujo 2012/7/20 Johan Hendriks > Hello all. > > On my test machine with FreeBSD Current from 14-07-2012 i lost my zpool > due to a disconnected power supply. > I noticed when i do a zpool get all on a pool that is not active, zpool > core dumps. > I do not know if it should do this, but an error message that there are no > active pools would make it nicer. > > hast2 ~ # zpool status > pool: testpool > state: UNAVAIL > status: One or more devices could not be opened. There are insufficient > replicas for the pool to continue functioning. > action: Attach the missing device and online it using 'zpool online'. > see: http://illumos.org/msg/ZFS-**8000-3C > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > testpool UNAVAIL 0 0 0 > mirror-0 UNAVAIL 0 0 0 > 10238773687773245204 UNAVAIL 0 0 0 was > /dev/gpt/disk0 > 7739197258598802985 UNAVAIL 0 0 0 was > /dev/gpt/disk1 > hast2 ~ # zpool get all > Assertion failed: (nvlist_lookup_nvlist(config, "feature_stats", > &features) == 0), file /usr/src/cddl/lib/libzfs/../..** > /../cddl/contrib/opensolaris/**lib/libzfs/common/libzfs_**config.c, line > 250. > Abort trap: 6 (core dumped) > > It leaves a core file > -rw------- 1 root wheel 8990720 Jul 20 12:20 zpool.core > > Also a zpool get all testpool coredumps. > > regards > Johan Hendriks > Neuteboom Automatisering > ______________________________**_________________ > 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 > " > -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Fri Jul 20 13:02:11 2012 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 5B1B9106566B; Fri, 20 Jul 2012 13:02:11 +0000 (UTC) (envelope-from db@nipsi.de) Received: from fop.bsdsystems.de (mx.bsdsystems.de [88.198.57.43]) by mx1.freebsd.org (Postfix) with ESMTP id 783A88FC0A; Fri, 20 Jul 2012 13:02:10 +0000 (UTC) Received: from wuerschtl.global.intra.guj.com (fwhide.guj.de [193.7.250.35]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by fop.bsdsystems.de (Postfix) with ESMTP id 487EE216C2A; Fri, 20 Jul 2012 15:02:09 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1084) From: dennis berger In-Reply-To: <20120720123255.GA56250@FreeBSD.org> Date: Fri, 20 Jul 2012 15:02:08 +0200 Message-Id: References: <7FE7A5F3-53FF-4508-A3D6-562E8FA9764D@nipsi.de> <20120720123255.GA56250@FreeBSD.org> To: John X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ISCSI on zvols with two maschines. What needs to be done? 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, 20 Jul 2012 13:02:11 -0000 Hi John, see inline. Am 20.07.2012 um 14:32 schrieb John: > Hi Dennis, >=20 > ----- dennis berger's Original Message ----- >> Hi folks, >>=20 >> The following question often comes to me, when I speak to my = customers. >>=20 >> Is it possible to attach two systems to the same storage array using = shared SAS and use istgt + zfs to provide=20 >> a reliable ISCSI target. This could be active/passive or later = active/active. In case it's not possible, what needs to be done? >>=20 >> The questions that came into my mind. >>=20 >> Can I connect two freebsd to the storage and boot them up? Just that = both systems would see the physical devices.=20 >=20 > Yes, please see: >=20 > http://people.freebsd.org/~jwd/zfsnfsserver.jpg This is exactly how I would like to use it. >=20 > for a possible diagram. Dual path all the shelves and use gmultipath = to > access them. Use 9-stable. OK. And with new multipath code. I remember I read something in = quarterly reports=85 >=20 > Make sure each host is dual homed and a client (initiator) can access > the target with dual pathing, one connection over each network path. >=20 OK but it's still accessing one target right. >> Can I start ZFS on both systems without writing on it? I would like = to use just block devices for ISCSI. Is everything still consistent? >=20 > You can start ZFS on both systems and import different pools. The same = pool > cannot be imported on two different systems (you can, you won't be = happy). >=20 Ahh you mean to create a separate zfs pool with the different devices = names according to multipath. Which in in essence are the same physical = devices?! PoolA with da0 and da2=20 PoolB with da1 and da3 =20 da0 and da1 are the same device but different paths? But where is the difference?! Maybe I don't understand exactly why 2 = pools >> Does starting ZFS up already writing some sort of meta data to the = physical devices?! >=20 > Yes, others would know better than I. OK >=20 >> Can I start istgt on both systems without actually using the istgt on = one system?! Then CARP would be enough, wouldn't it. >=20 > You start istgt on both systems handing out luns from the two = different > pools you have mounted on each head. Hint, put your istgt configs for > each pool in each pool. >=20 > Using CARP/DEVD and some shell code, if head A dies, you import the > failing heads pool on the other system and bring istgt up. CARP = handles > the IP address switch over. Do I need to zfs import?!=20 -dennis >=20 >> Or in case of active/active extend istgt to communicate with the = other istgt to not hand out a device twice?=20 >=20 > Not sure I'd want to expend the effort here. Just an opinion. >=20 > Hope this helps. >=20 > -John >=20 >> Best, >> -dennis >=20 Dipl.-Inform. (FH) Dennis Berger email: db@bsdsystems.de mobile: +491791231509 fon: +494054001817 From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 00:22:43 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CDED106566B for ; Sat, 21 Jul 2012 00:22:43 +0000 (UTC) (envelope-from sam@athyriogames.com) Received: from madonna.sslcatacombnetworking.com (madonna.sslcatacombnetworking.com [174.133.19.130]) by mx1.freebsd.org (Postfix) with ESMTP id 276DD8FC16 for ; Sat, 21 Jul 2012 00:22:43 +0000 (UTC) Received: from c-98-206-215-156.hsd1.in.comcast.net ([98.206.215.156] helo=laptopv) by madonna.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1SsN4f-0007rV-8q for freebsd-fs@freebsd.org; Fri, 20 Jul 2012 18:57:33 -0500 From: "Sam Zehr" To: Date: Fri, 20 Jul 2012 19:05:15 -0500 Message-ID: <01bf01cd66d4$84756b40$8d6041c0$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1m1IGSCDeEA97+S7qCQ7u+tb9g1g== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - madonna.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Boot disk read-only? 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, 21 Jul 2012 00:22:43 -0000 Hello all. I apologize if this is the wrong place to ask, but I've had good luck with USB questions in the USB list, so I thought this would be the place. How do I make a disk in FreeBSD 9.0 _completely_ read-only? I am converting an embedded system using flash for a disk from BSD 7.0 to 9.0 rc.initdiskless is working I had luck with BSD 7.0 by doing the following additional steps: 1. Add noatime to fstab options 2. Add vfs.nfs.diskless_valid=1 to /boot/loader.conf So far this is not working on BSD 9.0. It looks like something is changing on the disk during boot The disk is a USB thumb drive Sysctl vfs.nfs.diskless_valid returns 0 once booted up Please note that I am not just concerned about files - the entire disk needs to be locked, like ROM. Is there a way to completely lock the disk, even during the boot? Or perhaps a reason why setting vfs.nfs.diskless_valid=1 in /boot/loader.conf does not appear to work? Thanks Sam From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 00:32:33 2012 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 4C9381065673 for ; Sat, 21 Jul 2012 00:32:33 +0000 (UTC) (envelope-from lists@mawer.org) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C87118FC17 for ; Sat, 21 Jul 2012 00:32:32 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so1587769vcb.13 for ; Fri, 20 Jul 2012 17:32:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-google-sender-delegation:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding:x-gm-message-state; bh=tUM5WfuDBRsEhIzzwY6P3CsHirIaE6FD3JCliGbaRk8=; b=kVx+XCFmQQG6459veMGpbTaz28a/khykDsMydUBnV7lOWBCr+9ekKBsxqZLcIKFXHF idQQxqls4a7UEK6sB+FN420lvvacjS7MuGXm2XWcqFs/3ftGMAfLx1OTny9jr7YsO7I8 Lx9SGR7YcwfWM2HHAtNnQRXs3/wNZqGyUhjlKH9FVnNPtHfFb4LYZYQxc+tP1cJ2HuJl 6T8dwwAiv/++bJwqrK+Nq/qeEeRjBoEsAJDxXuyBGQ+o342bwpbty6hXS5GcNtO+Ibie DVVUFoAvMzldZxVI+vaunoV+ElJ51OshnTh/FiWggfqhaZSsrAdKCt0/VtGdhOaLUum/ VGWw== MIME-Version: 1.0 Received: by 10.52.88.170 with SMTP id bh10mr5286287vdb.11.1342830752013; Fri, 20 Jul 2012 17:32:32 -0700 (PDT) Sender: antony@mawer.org X-Google-Sender-Delegation: antony@mawer.org Received: by 10.52.181.194 with HTTP; Fri, 20 Jul 2012 17:32:31 -0700 (PDT) In-Reply-To: References: <50064FB2.3020409@entel.upc.edu> Date: Sat, 21 Jul 2012 10:32:31 +1000 X-Google-Sender-Auth: Nh4i2M0CH9XCmU3nBE5U8HLGwnY Message-ID: From: Antony Mawer To: attilio@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmKQfRDHL+qXMEggDPJWLoON1NK4KhDl+pImHPJCLWCYxNYhmx3TT4PlPRR8lruALOREXk4 Cc: FreeBSD FS , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions 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, 21 Jul 2012 00:32:33 -0000 On Wed, Jul 18, 2012 at 6:45 PM, Attilio Rao wrote: > 2012/7/18, Gustau P=E9rez i Querol : >> >> Sorry fo the delay. >> >> About the ntfs support, I'd go with fuse and leave the most relevant >> filesystems in kernel space. In fact filesystems not particulary >> specific and not tied our kernel would go to userspace; thinks like >> smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the >> list is incomplete and I don't really know if all of them are yet >> implemenent in userspace) in my opinion. That would make them easier to >> maintain (changes in the kernel would only affect fuse, once fixed all >> the userspace filesystem would work again). >> >> As a bonus, we would get many working fs based on fuse. In the >> server side gluster is a desirable thing; in the desktop things like >> gvfs (in the linux world gvfs is used not only by gnome but also by kde >> or xfce) or truecrypt > > I'm really concerned also about ntfs and smbfs at the moment. It seems > that there is also a FUSE smbfs port, but I never used it and I'm not > sure about its state at all. >From what I understand, Apple have done a considerable amount of work on the FreeBSD-drived smbfs in the latest versions of OS X, based on the existing smbfs in tree: http://www.opensource.apple.com/source/smb/smb-552.5/ I imagine things like the filesystem locking are probably somewhat different, but in terms of updating smbfs itself to support newer features it may be a good base (licensing permitting). smbfs at the moment lacks in some areas such as DFS support, although I do not know if the OS X version is any different there (given the consumer focus of their OS, probably not). There was also a version spun off by OpenSolaris: http://hub.opensolaris.org/bin/view/Project+smbfs/ which again was based on the FreeBSD + Apple versions. I also have a vested interest in NWFS continuing to work - only from a legacy point of view where we still interoperate with a number of Netware 6 servers through this. While those will likely eventually go away, more than likely before we move to 10.x, if there is anyone capable of working on it we could supply a test environment. Unfortunately the actual locking of the NWFS and NCP modules is outside my sphere of knowledge... -- Antony From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 02:35:46 2012 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 58A9E106564A; Sat, 21 Jul 2012 02:35:46 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 203FD8FC08; Sat, 21 Jul 2012 02:35:46 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SsPXd-000G8N-Kv; Fri, 20 Jul 2012 22:35:37 -0400 Date: Fri, 20 Jul 2012 22:35:37 -0400 From: Gary Palmer To: dennis berger Message-ID: <20120721023537.GB19321@in-addr.com> References: <7FE7A5F3-53FF-4508-A3D6-562E8FA9764D@nipsi.de> <20120720123255.GA56250@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, John Subject: Re: ISCSI on zvols with two maschines. What needs to be done? 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, 21 Jul 2012 02:35:46 -0000 On Fri, Jul 20, 2012 at 03:02:08PM +0200, dennis berger wrote: > Hi John, > see inline. > > > Am 20.07.2012 um 14:32 schrieb John: > > > Hi Dennis, > > > > ----- dennis berger's Original Message ----- > >> Hi folks, > >> > >> The following question often comes to me, when I speak to my customers. > >> > >> Is it possible to attach two systems to the same storage array using shared SAS and use istgt + zfs to provide > >> a reliable ISCSI target. This could be active/passive or later active/active. In case it's not possible, what needs to be done? > >> > >> The questions that came into my mind. > >> > >> Can I connect two freebsd to the storage and boot them up? Just that both systems would see the physical devices. > > > > Yes, please see: > > > > http://people.freebsd.org/~jwd/zfsnfsserver.jpg > > This is exactly how I would like to use it. > > > > > for a possible diagram. Dual path all the shelves and use gmultipath to > > access them. Use 9-stable. > OK. And with new multipath code. I remember I read something in quarterly reports? > > > > > Make sure each host is dual homed and a client (initiator) can access > > the target with dual pathing, one connection over each network path. > > > OK but it's still accessing one target right. > > >> Can I start ZFS on both systems without writing on it? I would like to use just block devices for ISCSI. Is everything still consistent? > > > > You can start ZFS on both systems and import different pools. The same pool > > cannot be imported on two different systems (you can, you won't be happy). > > > Ahh you mean to create a separate zfs pool with the different devices names according to multipath. Which in in essence are the same physical devices?! > > PoolA with da0 and da2 > PoolB with da1 and da3 > > da0 and da1 are the same device but different paths? > But where is the difference?! Maybe I don't understand exactly why 2 pools You cannot have both systems accessing the same device, whether in one pool or in two pools, at the same time. You will end up with trouble. The two pools in John's reply indicated that each system would have its own pool of disks. > >> Does starting ZFS up already writing some sort of meta data to the physical devices?! > > > > Yes, others would know better than I. > > OK > > > > >> Can I start istgt on both systems without actually using the istgt on one system?! Then CARP would be enough, wouldn't it. > > > > You start istgt on both systems handing out luns from the two different > > pools you have mounted on each head. Hint, put your istgt configs for > > each pool in each pool. > > > > Using CARP/DEVD and some shell code, if head A dies, you import the > > failing heads pool on the other system and bring istgt up. CARP handles > > the IP address switch over. > > Do I need to zfs import?! This is the key bit. What John suggests is that on system A you have poolA and on system B you have pool B. Both pools have their own, separate, disks. If system A goes down, system B notices this and imports poolA and shares out its iSCSI devices. You have to be careful when system A comes back up that it doesn't auto-import the pool and negotiates with system B to get it back It may be easier to think of a situation where there is only 1 pool. In this situation, the two servers will be in active/passive mode, and the passive system will only ever take load if the active node goes down. The important thing to remember is NO filesystem which is included with FreeBSD by default is cluster aware. This means that two servers CANNOT both mount filesystems on direct-attached storage without corrupting the data on the storage. The best you can get active/passive right now, where only 1 server mounts the filesystem at a time and the second server takes over in event of failure of the primary server. In this instance consider ZFS, even at the zpool layer, to be a filesystem. Mounting the same zpool from shared storage on two servers at the same time will almost certainly lead to corruption and probably a restore from backup tapes. Gary From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 11:50:33 2012 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 5B3F7106566B for ; Sat, 21 Jul 2012 11:50:33 +0000 (UTC) (envelope-from rafi@ugcs.caltech.edu) Received: from fox.seas.upenn.edu (foxv6.seas.upenn.edu [IPv6:2607:f470:8:64:5ea5::e]) by mx1.freebsd.org (Postfix) with ESMTP id F3A148FC08 for ; Sat, 21 Jul 2012 11:50:32 +0000 (UTC) Received: from [158.130.106.226] (seas737.wireless-pennnet.upenn.edu [158.130.106.226]) (authenticated bits=0) by fox.seas.upenn.edu (8.14.5/8.14.3) with ESMTP id q6LBoVov022873 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Sat, 21 Jul 2012 07:50:31 -0400 Message-ID: <500A9787.5060109@ugcs.caltech.edu> Date: Sat, 21 Jul 2012 07:50:31 -0400 From: Rafi Rubin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4 MIME-Version: 1.0 To: freebsd-fs@freebsd.org X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-07-21_03:2012-07-20, 2012-07-21, 1970-01-01 signatures=0 X-PP-Spam-Details: rule=add_spam_details policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1207210082 Subject: ZFS deadlock 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, 21 Jul 2012 11:50:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a small server with a mirrored pair of hard drives that handles generally light loads for a number of linux machines over nfs v3. I've been seeing some deadlocks (and possibly worse) lately. I've narrowed down the freezing to a simple test run simultaneously on a number of the client machines: mount host:/food/bar ls bar/.zfs/snapshot When I do that, all the client machines hang on any access to the server. On the server, only the volume "bar" hangs, the rest are fine. This occurs even when there is no other load on the server. Also, after rebooting the server, the client machines eventually complete the ls and behave normally. I think this doesn't happen if the directory is cached, either in memory or on an L2 ssd, but I need to rerun some tests. For now the machine seems to be stable with nfsd limited to a single thread. Any help debugging would be appreciated, Rafi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQCpeEAAoJEPILXytRLnK22rAQAJpEc9hVdfrNaqJLbqf1mwiJ kzLAh2FHmhzWvomA6WBdpR5JZ535vkQjcd3gS9KdKjmX+KxozTGM+CiX8quJwVef nLOXqY5KNqDLQVpfJtMbo+XybM6nmLN8YImX/wIAbVXtRYwOPLP/9yk5aYywZnPN MFhQrh/PnMydUYJwYfZHdEGACnVJnPWord9p9OD7O7FxsItMPMDNRZPrLr2BEHPm LheVqXSXsvBe8w/CtQXoyCvWRr9J+bA2/Djid6RNpUMH7S8f6+xKzlYxrivVyFjY s88NiCbDrOefNEJMldsBeSrC/G3ZTM2iMZMr7KV9hqGbp9rJvth9KZsoGkpjyA9F //z1LNjUVoc+ol1z0oooNKpPSEvYCU/21mTZ9lZ0p9FeRSti2jH33zyYXmv5N8TO 6pjkO14TpBby/j1uNI3CxKGp3XN/o67AkpCBcJFQqfmFC2o0wx6f1PTqbAvSIwR3 M+srT/plBIx0CI53WYMnSunaw126ZxbiT9UiK+7OoAwXT5v62Wi7bWU0Jd5Ezbvc 8Bo+RbkVnEuLW0xTr0gbEXJy2m3/Gmq+G570D7bEqiXdZG3gpcehXEZ9tCStQ1ZM QNtf7lFmgamsBETyiaIbj9U0fDd/1Uddp5dHjxccF5qOBs7CNnCdJ+YAcpkT+Rup KMPYRNrdyABggVIrkkPg =4BS7 -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 15:04:04 2012 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 4F7B8106566B for ; Sat, 21 Jul 2012 15:04:04 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id E95AA8FC0A for ; Sat, 21 Jul 2012 15:04:03 +0000 (UTC) Received: from [192.168.179.45] (hmbg-4d069621.pool.mediaWays.net [77.6.150.33]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LckK3-1TbJhz1wJj-00k1DZ; Sat, 21 Jul 2012 17:03:56 +0200 Message-ID: <500AC46D.309@brockmann-consult.de> Date: Sat, 21 Jul 2012 17:02:05 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120601 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <500A9787.5060109@ugcs.caltech.edu> In-Reply-To: <500A9787.5060109@ugcs.caltech.edu> X-Provags-ID: V02:K0:OHlva2mWPTVIgsLQcEZ/GWF+460rc/7ptSvpT2mNNCe aI+XRS6+SEuocO0w0bJmyTENG4G/HmtYSHJD4bDLCtVT2lvkOI k4IirF1V0UvZifR69lI/NBF0iFLIvZyNTpj2IK13aGVn+N4gFh LaD06gSmCa9cDDY+ustVqymASWlpDHaDIC6j/Jkn47gRrQMopN q3pJzE3tMErapDa9DN8aLrSwhX8WDg8h40qS0aqfuKEOS7HxOm rVvJKXTeyO1LQqn8NAMyc0Y46W97CtvtrkDUzGmFvfviX7TSSe nlHjeDOOIX78CO5FBXDNaOZlWCZnGQBL3TVXwHMLMYL1HkWHwr 99xIakzfTPTLXPV+klLY8/HaHarDWnFph03Rn+Ku1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS deadlock 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, 21 Jul 2012 15:04:04 -0000 I've had the same thing happen. It only happens with Linux clients. My workaround is to mount an empty directory on top of .zfs. I submitted a PR about it also. And I can't reproduce it on other machines, including the replicated backup server with all the same snapshots. It only happens on the one production machine, possibly because it has more nfs clients active than what I created for my tests. Here's my forum thread: http://forums.freebsd.org/showthread.php?t=29648 Here's my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/168947 On 07/21/2012 01:50 PM, Rafi Rubin wrote: > I have a small server with a mirrored pair of hard drives that handles > generally light loads for a number of linux machines over nfs v3. > > I've been seeing some deadlocks (and possibly worse) lately. I've > narrowed > down the freezing to a simple test run simultaneously on a number of the > client machines: > > mount host:/food/bar > ls bar/.zfs/snapshot > > When I do that, all the client machines hang on any access to the > server. On > the server, only the volume "bar" hangs, the rest are fine. > > This occurs even when there is no other load on the server. Also, after > rebooting the server, the client machines eventually complete the ls and > behave normally. > > > I think this doesn't happen if the directory is cached, either in > memory or on > an L2 ssd, but I need to rerun some tests. > > For now the machine seems to be stable with nfsd limited to a single > thread. > > > Any help debugging would be appreciated, > Rafi > _______________________________________________ > 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 Sat Jul 21 15:32:16 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FD3A106566C; Sat, 21 Jul 2012 15:32:16 +0000 (UTC) (envelope-from rmh.aybabtu@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 089AC8FC19; Sat, 21 Jul 2012 15:32:15 +0000 (UTC) Received: by yhfs35 with SMTP id s35so5538435yhf.13 for ; Sat, 21 Jul 2012 08:32:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=6SRG6IJ2L44flKx1KPrVuxh89FjfX+26ckMXV00ZE+E=; b=VuckSj1Pxqmb9I+3+xl0HQ1fSBsxZbCcQ426pCuWyNIsQlTH519aOiTL9qNA1+rjmV IbOuMiub/HVLxctpaiSJf4c52YgcZQp1Adi2kcgv/3uv/cVD+wfUeagARI7mycxHbCu2 8xdXCixVuWXgl0B0kJDPSkaJ+odRoD+W6avTOFzAiLIRpcxbfmoUOcPQjAZYGiaobMCp SroQA9bZc5PnBXoN34DdoA2YOpQoHIHkkMZk8Vzzr6RcTw1dl8+X1wG6DkhBe6EnWFEJ RA7jWv4p3wpEWADiCG7nq6n0B4hFsCHB0u5mkEvQwzrS39EpmQGvmeQbyZUF/ZxVK0uP G+ug== MIME-Version: 1.0 Received: by 10.50.220.136 with SMTP id pw8mr7039189igc.1.1342884735117; Sat, 21 Jul 2012 08:32:15 -0700 (PDT) Sender: rmh.aybabtu@gmail.com Received: by 10.42.136.7 with HTTP; Sat, 21 Jul 2012 08:32:15 -0700 (PDT) Date: Sat, 21 Jul 2012 17:32:15 +0200 X-Google-Sender-Auth: 0dhaV19AmNR3SqpT39eNiwtRLyE Message-ID: From: Robert Millan To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Kostik Belousov Subject: KBI bump in r227697? 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, 21 Jul 2012 15:32:16 -0000 Hi all, Kostik, I was just reading through r227697, and it seems to me that this commit changes KBI. Shouldn't this have a __FreeBSD_version bump? My concern is with external file system modules like fuse4bsd (although on first sight it doesn't seem that fuse4bsd is affected). http://lists.freebsd.org/pipermail/svn-src-all/2011-November/044647.html -- Robert Millan From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 18:55:51 2012 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 B668F1065670; Sat, 21 Jul 2012 18:55:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 316F68FC0A; Sat, 21 Jul 2012 18:55:51 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q6LIu0jT032485; Sat, 21 Jul 2012 21:56:00 +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.5/8.14.5) with ESMTP id q6LItl0i040472; Sat, 21 Jul 2012 21:55:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q6LItlTv040471; Sat, 21 Jul 2012 21:55:47 +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, 21 Jul 2012 21:55:47 +0300 From: Konstantin Belousov To: Robert Millan Message-ID: <20120721185547.GD2676@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P0uLJ1D0dtZMuM2h" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 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 Cc: freebsd-fs@freebsd.org Subject: Re: KBI bump in r227697? 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, 21 Jul 2012 18:55:51 -0000 --P0uLJ1D0dtZMuM2h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 21, 2012 at 05:32:15PM +0200, Robert Millan wrote: > Hi all, Kostik, >=20 > I was just reading through r227697, and it seems to me that this > commit changes KBI. Shouldn't this have a __FreeBSD_version bump? >=20 > My concern is with external file system modules like fuse4bsd > (although on first sight it doesn't seem that fuse4bsd is affected). >=20 > http://lists.freebsd.org/pipermail/svn-src-all/2011-November/044647.html This is r229703 for stable/9. The __FreeBSD_version was already bumped after that change, at least 3 time= s. In fact, the bump to 900501 in r229723 is almost immediately after it. For HEAD, it makes no sense to bump the revision at all, since you are assumed to always run latest HEAD. --P0uLJ1D0dtZMuM2h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAK+zMACgkQC3+MBN1Mb4h5fgCgk0QWUwDHwOBJRUNJ71fZ33C+ cBcAoLgISquzaymGsMwDMxdtNwJ0ZkuG =dz9c -----END PGP SIGNATURE----- --P0uLJ1D0dtZMuM2h-- From owner-freebsd-fs@FreeBSD.ORG Sat Jul 21 19:08:35 2012 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 465E51065670 for ; Sat, 21 Jul 2012 19:08:35 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 1B7F98FC1D for ; Sat, 21 Jul 2012 19:08:35 +0000 (UTC) Received: from [192.168.135.103] (c-76-126-166-136.hsd1.ca.comcast.net [76.126.166.136]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q6LJ8Scn075633 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 21 Jul 2012 12:08:29 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <500AFE27.9000700@feral.com> Date: Sat, 21 Jul 2012 12:08:23 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20120721185547.GD2676@deviant.kiev.zoral.com.ua> In-Reply-To: <20120721185547.GD2676@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Sat, 21 Jul 2012 12:08:29 -0700 (PDT) Subject: Re: KBI bump in r227697? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 19:08:35 -0000 > This is r229703 for stable/9. > The __FreeBSD_version was already bumped after that change, at least 3 times. > In fact, the bump to 900501 in r229723 is almost immediately after it. > > For HEAD, it makes no sense to bump the revision at all, since you are > assumed to always run latest HEAD. Really? This puzzles me. You're not really supposed to make KBI changes in stable- otherwise stable isn't a stable place for vendor KOBJs. When you make KBI changes, independent of whether head or not, a revision bump is useful so that dependent code knows when it has to change. This change carries forward and backwards for compilation independent of which branch this is in.