headers
linimon | 17 May 2013 23:56
Picon
Favicon

Re: kern/178713: [nfs] [patch] Correct WebNFS support in NFS server and client from sys/fs

Old Synopsis: Correct WebNFS support in NFS server and client from sys/fs
New Synopsis: [nfs] [patch] Correct WebNFS support in NFS server and client from sys/fs

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-fs
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri May 17 21:56:04 UTC 2013
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=178713
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
System Integrated | 16 May 2013 22:20
Picon
Favicon

Re: kern/153680: [xfs] 8.1 failing to mount XFS partitions

The following reply was made to PR kern/153680; it has been noted by GNATS.

From: System Integrated <info <at> system-integrated.de>
To: bug-followup <at> FreeBSD.org, jan0sch <at> gmx.net
Cc:  
Subject: Re: kern/153680: [xfs] 8.1 failing to mount XFS partitions
Date: Thu, 16 May 2013 22:03:37 +0200

 Hey there,

 if got the exact same error on FreeBSD 9.0-RELEASE and 9.1-RELEASE.
 The bug prevents me to migrate from linux to freebsd on some systems.

 Needs to be fixed, i guess.

 Kind regards
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Outback Dingo | 15 May 2013 14:13
Picon

FreeBSD 9-RELEASE zpool Out of File Descriptors ??

So it seems a new deployment we just built with zfsonroot mirror and a 48TB
master pool is already out of File Descriptors???

  pool: master
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support
feature
        flags.
  scan: none requested
config:

        NAME                      STATE     READ WRITE CKSUM
        master                    ONLINE       0     0     0
          raidz3-0                ONLINE       0     0     0
            multipath/SATA_LUN01  ONLINE       0     0     0
            multipath/SATA_LUN03  ONLINE       0     0     0
            multipath/SATA_LUN04  ONLINE       0     0     0
            multipath/SATA_LUN05  ONLINE       0     0     0
            multipath/SATA_LUN07  ONLINE       0     0     0
            multipath/SATA_LUN08  ONLINE       0     0     0
            multipath/SATA_LUN09  ONLINE       0     0     0
            multipath/SATA_LUN10  ONLINE       0     0     0
          raidz3-1                ONLINE       0     0     0
            multipath/SATA_LUN11  ONLINE       0     0     0
            multipath/SATA_LUN12  ONLINE       0     0     0
            multipath/SATA_LUN13  ONLINE       0     0     0
            multipath/SATA_LUN14  ONLINE       0     0     0
(Continue reading)

Permalink | Reply | 14 comments |
headers
FreeBSD bugmaster | 13 May 2013 13:06
Picon
Favicon

Current problem reports assigned to freebsd-fs <at> FreeBSD.org

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/178412  fs         [smbfs] Coredump when smbfs mounted
o kern/178388  fs         [zfs] [patch] allow up to 8MB recordsize
o kern/178349  fs         [zfs] zfs scrub on deduped data could be much less see
o kern/178329  fs         [zfs] extended attributes leak
o kern/177985  fs         [zfs] disk usage problem when copying from one zfs dat
o kern/177971  fs         [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3,
o kern/177966  fs         [zfs] resilver completes but subsequent scrub reports 
o kern/177658  fs         [ufs] FreeBSD panics after get full filesystem with uf
o kern/177536  fs         [zfs] zfs livelock (deadlock) with high write-to-disk 
o kern/177445  fs         [hast] HAST panic
o kern/177240  fs         [zfs] zpool import failed with state UNAVAIL but all d
o kern/176978  fs         [zfs] [panic] zfs send -D causes "panic: System call i
o kern/176857  fs         [softupdates] [panic] 9.1-RELEASE/amd64/GENERIC panic 
o bin/176253   fs         zpool(8): zfs pool indentation is misleading/wrong
o kern/176141  fs         [zfs] sharesmb=on makes errors for sharenfs, and still
o kern/175950  fs         [zfs] Possible deadlock in zfs after long uptime
o kern/175897  fs         [zfs] operations on readonly zpool hang
o kern/175179  fs         [zfs] ZFS may attach wrong device on move
o kern/175071  fs         [ufs] [panic] softdep_deallocate_dependencies: unrecov
o kern/174372  fs         [zfs] Pagefault appears to be related to ZFS
o kern/174315  fs         [zfs] chflags uchg not supported
(Continue reading)

Permalink | Reply | 0 comments |
headers
linimon | 10 May 2013 05:36
Picon
Favicon

Re: kern/178467: [request] Optimized Checksum Code for ZFS

Old Synopsis: Optimized Checksum Code for ZFS
New Synopsis: [request] Optimized Checksum Code for ZFS

State-Changed-From-To: open->suspended
State-Changed-By: linimon
State-Changed-When: Fri May 10 03:35:38 UTC 2013
State-Changed-Why: 
assign, and note that someone will need to provide a patch.

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-fs
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri May 10 03:35:38 UTC 2013
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=178467
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Outback Dingo | 9 May 2013 14:31
Picon

Corrupted zpool import -f FAILS state FAULTED

ok zfsgurus, FreeBSD 9.1-STABLE box zpool import -f reports pool status
Faulted, one of more devices contains corrupted data, however its showing
the guid as faulted in the poll, and not the actual disk device /dev/daX,
the pool is a single vdev 24 disk raidz3. Essentially the hardward platform
is a dual node system, with 8 enclosures connected to 24 SAS drives via 4
LSI cards. I am not currently using geom_multipath, but the box is zoned so
that each node can see 50% of the drives,
in case of Failure, carp kicks in and migrates "zpool import -af" the pools
onto the other node. it seems as though somehow the pool is now seeing guid
and not devices, not sure if they have switched devices ids due to a reboot.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 4 comments |
headers
Steven Hartland | 9 May 2013 00:20
Picon
Favicon

Re: kern/178388: [zfs] [patch] allow up to 8MB recordsize

The following reply was made to PR kern/178388; it has been noted by GNATS.

From: "Steven Hartland" <smh <at> freebsd.org>
To: <bug-followup <at> freebsd.org>,
	<nowak <at> tepeserwery.pl>
Cc:  
Subject: Re: kern/178388: [zfs] [patch] allow up to 8MB recordsize
Date: Wed, 8 May 2013 23:12:04 +0100

 Seems interesting but it's really something that needs to be
 reviewed and submitted upstream (illumos).
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Brendan Gregg | 8 May 2013 23:35
Favicon

Re: Strange slowdown when cache devices enabled in ZFS

Freddie Cash wrote (Mon Apr 29 16:01:55 UTC 2013):
|
| The following settings in /etc/sysctl.conf prevent the "stalls"
completely,
| even when the L2ARC devices are 100% full and all RAM is wired into the
| ARC.  Been running without issues for 5 days now:
|
| vfs.zfs.l2arc_norw=0                                  # Default is 1
| vfs.zfs.l2arc_feed_again=0                         # Default is 1
| vfs.zfs.l2arc_noprefetch=0                          # Default is 0
| vfs.zfs.l2arc_feed_min_ms=1000                 # Default is 200
| vfs.zfs.l2arc_write_boost=320000000           # Default is 8 MBps
| vfs.zfs.l2arc_write_max=160000000             # Default is 8 MBps
|
| With these settings, I'm also able to expand the ARC to use the full 128
GB
| of RAM in the biggest box, and to use both L2ARC devices (60 GB in total).
| And, can set primarycache and secondarycache to all (the default) instead
| of just metadata.
|[...]

The thread earlier described a 100% CPU-bound l2arc_feed_thread, which
could be caused by these settings:

vfs.zfs.l2arc_write_boost=320000000           # Default is 8 MBps
vfs.zfs.l2arc_write_max=160000000             # Default is 8 MBps

If I'm reading that correctly, it's increasing the write max and boost to
be 160 Mbytes and 320 Mbytes. To satisfy these, the L2ARC must scan memory
from the tail of the ARC lists, lists which may be composed of tiny buffers
(Continue reading)

Permalink | Reply | 4 comments |
headers
FreeBSD bugmaster | 6 May 2013 13:06
Picon
Favicon

Current problem reports assigned to freebsd-fs <at> FreeBSD.org

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/178349  fs         [zfs] zfs scrub on deduped data could be much less see
o kern/178329  fs         [zfs] extended attributes leak
o kern/177985  fs         [zfs] disk usage problem when copying from one zfs dat
o kern/177971  fs         [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3,
o kern/177966  fs         [zfs] resilver completes but subsequent scrub reports 
o kern/177658  fs         [ufs] FreeBSD panics after get full filesystem with uf
o kern/177536  fs         [zfs] zfs livelock (deadlock) with high write-to-disk 
o kern/177445  fs         [hast] HAST panic
o kern/177240  fs         [zfs] zpool import failed with state UNAVAIL but all d
o kern/176978  fs         [zfs] [panic] zfs send -D causes "panic: System call i
o kern/176857  fs         [softupdates] [panic] 9.1-RELEASE/amd64/GENERIC panic 
o bin/176253   fs         zpool(8): zfs pool indentation is misleading/wrong
o kern/176141  fs         [zfs] sharesmb=on makes errors for sharenfs, and still
o kern/175950  fs         [zfs] Possible deadlock in zfs after long uptime
o kern/175897  fs         [zfs] operations on readonly zpool hang
o kern/175179  fs         [zfs] ZFS may attach wrong device on move
o kern/175071  fs         [ufs] [panic] softdep_deallocate_dependencies: unrecov
o kern/174372  fs         [zfs] Pagefault appears to be related to ZFS
o kern/174315  fs         [zfs] chflags uchg not supported
o kern/174310  fs         [zfs] root point mounting broken on CURRENT with multi
o kern/174279  fs         [ufs] UFS2-SU+J journal and filesystem corruption
(Continue reading)

Permalink | Reply | 0 comments |
headers
linimon | 4 May 2013 23:38
Picon
Favicon

Re: kern/178329: [zfs] extended attributes leak

Synopsis: [zfs] extended attributes leak

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-fs
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat May 4 21:38:43 UTC 2013
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=178329
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Daniel Feenberg | 4 May 2013 21:08
Favicon

Restarting exports disturbs NFS clients


When we change the exportfs file on our FreeBSD 9.1 fileserver and signal
mountd to reread the file:

    kill -HUP `cat /var/run/mountd.pid`

it kills the jobs on  clients that have files open on the fileserver. They
terminate with an I/O error. The same thing happens if NFS is restarted.

This is pretty inconvenient for users (and us). Is there a way around 
this? We have noticed that a Linux fileserver can restart nfs without 
distrubing clients (other than a short pause). The Linux restart doesn't 
restart the locking mechanism - is that the difference? We could do 
without locks, even without NFSv4, for that matter, if it would let us 
change exports without disturbing users. Perhaps there is an NFS shutdown 
procedure that we should be using?

Daniel Feenberg
NBER
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |

Gmane