kern/167260: msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists
>Number: 167260 >Category: kern >Synopsis: msdosfs disk was mounted the second time when the first umount >was not clean and mount record still exists >Confidential: no >Severity: serious >Priority: high >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 07:10:08 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Yuri >Release:9.0 amd64 >Organization: n/a >Environment: >Description: I had the broken flash disk, and few write operations failed. And umount operation hanged. So I had to pull the USB drive out. After checking, I mounted it again, and it works now. However, mount command shows it mounted twice (!!!): Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1 7753672 703904071463291%/mnt/fat1 /dev/da0s1 7753672 76014478498%/mnt/fat1 === log of the failed disk operations === ugen3.3: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:7:0:-1: Attached to scbus7 da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 7580MB (15523840 512 byte sectors: 255H 63S/T 966C) g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5 g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5 g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5 g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5 fsync: giving up on dirty 0xfe02a583b000: tag devfs, type VCHR usecount 1, writecount 0, refcount 989 mountedhere 0xfe01378d9c00 flags () v_object 0xfe024d34c658 ref 0 pages 1025 lock type devfs: EXCL by thread 0xfe020d2a78c0 (pid 8156) dev da0s1 g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5 fsync: giving up on dirty 0xfe02a583b000: tag devfs, type VCHR usecount 1, writecount 0, refcount 989 mountedhere 0xfe01378d9c00 flags () v_object 0xfe024d34c658 ref 0 pages 1025 lock type devfs: EXCL by thread 0xfe0042809460 (pid 8168) dev da0s1 ugen3.3: at usbus3 (disconnected) umass0: at uhub3, port 3, addr 3 (disconnected) (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 1 refs (da0:umass-sim0:0:0:0): removing device entry Device da0s1 went missing before all of the data could be written to it; expect data loss. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/167260: msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists
The following reply was made to PR kern/167260; it has been noted by GNATS. From: Yuri To: bug-follo...@freebsd.org Cc: Subject: Re: kern/167260: msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists Date: Tue, 24 Apr 2012 00:33:57 -0700 mount -v shows more info: /dev/da0s1 on /mnt/fat1 (msdosfs, local, writes: sync 3 async 6, reads: sync 37 async 0, fsid 8e003200) /dev/da0s1 on /mnt/fat1 (msdosfs, local, writes: sync 30 async 15070, reads: sync 37 async 6, fsid 8d003200) ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/167261: [patch] Remove etc/pam.d/kde module from base system
>Number: 167261 >Category: misc >Synopsis: [patch] Remove etc/pam.d/kde module from base system >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 08:10:08 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Alberto Villa >Release: >Organization: >Environment: >Description: FreeBSD ships a KDE PAM module (kde) in base, but it's missing support for passwordless login (kde-np), and it doesn't really belong in base system. We have been shipping both modules via security/pam_kde port for six months, so, with my kde@ hat on, I ask to remove the one in base. >How-To-Repeat: >Fix: Well, it's quite trivial, nonetheless I attached a patch. Of course, etc/pam.d/kde has to be `svn rm`'d. Patch attached with submission follows: Index: Makefile === --- Makefile(revision 234197) +++ Makefile(working copy) @@ -7,7 +7,6 @@ cron \ ftpd \ imap \ - kde \ login \ other \ passwd pop3 \ Index: kde === --- kde (revision 234197) +++ kde (working copy) @@ -1,19 +0,0 @@ -# -# $FreeBSD$ -# -# PAM configuration for the "kde" service -# - -# auth -#auth sufficient pam_krb5.so no_warn try_first_pass -#auth sufficient pam_ssh.so no_warn try_first_pass -auth requiredpam_unix.so no_warn try_first_pass - -# account -accountrequiredpam_nologin.so -#account requiredpam_krb5.so -accountrequiredpam_unix.so - -# session -#session optionalpam_ssh.so want_agent -sessionrequiredpam_permit.so >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/167261: [patch] Remove etc/pam.d/kde module from base system
Synopsis: [patch] Remove etc/pam.d/kde module from base system Responsible-Changed-From-To: freebsd-bugs->miwi Responsible-Changed-By: miwi Responsible-Changed-When: Tue Apr 24 09:03:02 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=167261 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/167264: indian restaurant san diego
>Number: 167264 >Category: misc >Synopsis: indian restaurant san diego >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 12:00:26 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Vaughn Perez >Release:indian restaurant san diego >Organization: link building services >Environment: Gourmet Indian restaurant San Diego is making as well as offering delightful and healthy Indian meals in a relaxing and pleased atmosphere. Our selection card has been containing those native Indian meals San Diego recipes that stringently replicate the preparing custom of the large as well as gorgeous country of Indian. Our all the recipes are of extremely affordable rates. >Description: Many author become famous due to their thought as it give us an inspiration to select right one and to ignore what doesnt make impact on our life. For those quotes you just need a right visualization that suited your best. Now if you looking for wide collection of quote by famous writer whether it is old or new one, you must need a website that provide a large number quotes in one place with quality maintain subject and for all those seeker who are trying to get some valuable and inspirational quotes searchquotes.com has made their search over. At our site you can find a big range of quotes with profound meaning. As we know that customer time is valuable and no one wants to waste their time on searching some foolish quotes. With our web site you can get the categories for which you are seeking and preserve your time by receiving right one on your screen from specified category. These quotes make your sense of humor good in presence of friends, colleague, or in a work place where you live. For every mood you can select quotes from our class of quotes. Many people search in our vast category of quotes and some of these are quotes about moving on, insecurity quotes, paramour quotes, disappointment quotes, Gandalf quotes, a walk to remember quotes,lion king quotes, jealous quotes, stoner quotes, , quotes on being yourself, military wife quotes,demi lovato quotes, self discovery quotes and many more. In our site you can also post your valuable quotes and you can also check here some self discovery quote. Our goal is to have the best Self-discovery quotes on the web! For getting more detail about self discovery quotes , girly quotes , albus dumbledore quotes , will ferrell quotes , just visit to our web site at: http://www.searchquotes.com/search/Self-discovery/ >How-To-Repeat: Gourmet Indian restaurant San Diego is making as well as offering delightful and healthy Indian meals in a relaxing and pleased atmosphere. Our selection card has been containing those native Indian meals San Diego recipes that stringently replicate the preparing custom of the large as well as gorgeous country of Indian. Our all the recipes are of extremely affordable rates. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/167266: ZFS + new NFS export (sharenfs) leads to NAMEI leak
>Number: 167266 >Category: kern >Synopsis: ZFS + new NFS export (sharenfs) leads to NAMEI leak >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 14:20:13 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Oliver Brandmueller >Release:9-STABLE >Organization: >Environment: FreeBSD silver 9.0-STABLE FreeBSD 9.0-STABLE #9: Sun Apr 8 13:11:22 CEST 2012 root@silver:/usr/obj/usr/src/sys/BLACK amd64 >Description: If you NFS export a ZFS, create/remove of a file or directory lead to the leak of a NAMEI path buffer on the NFS server. This happens with new nfs (only NFSv3 tested) only, using the old NFS server does not trigger the NAMEI path buffer leak. An exported UFS on the same machine/environment does not trigger the behaviour. >How-To-Repeat: rc.conf: nfs_server_enable="YES" nfs_server_flags="-u -t -n 64" mountd_enable="YES" mountd_flags="/etc/zfs/exports" rpcbind_enable="YES" lockd_enable="YES" (mountd_flags not needed, if zfs_enable is set) Assuming, you have a USB stick or similar as /dev/da0 (it will probably even work with an md device): zpool create exptest /dev/da0 zfs sharenfs="-maproot=0 localhost" exptest # check with showmount -e exporting worked as expected mount localhost:/exptest /mnt cd /mnt vmstat -z | fgrep NAMEI echo test > foo vmstat -z | fgrep NAMEI rm foo vmstat -z | fgrep NAMEI you may repeat the creation/removal of the file several time and you will notice the NAMEI count increasing by one on each delete operation, no matter if file or directory. >Fix: No fix known. Workaround: using old NFS server. >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/167264: indian restaurant san diego
Synopsis: indian restaurant san diego State-Changed-From-To: open->closed State-Changed-By: thierry State-Changed-When: mar 24 avr 2012 16:13:46 UTC State-Changed-Why: Spam. Responsible-Changed-From-To: freebsd-bugs->thierry Responsible-Changed-By: thierry Responsible-Changed-When: mar 24 avr 2012 16:13:46 UTC Responsible-Changed-Why: Spam. http://www.freebsd.org/cgi/query-pr.cgi?pr=167264 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/167269: New port: devel/rubygem-backports backports ruby 1.9 api changes to 1.8
>Number: 167269 >Category: misc >Synopsis: New port: devel/rubygem-backports backports ruby 1.9 api >changes to 1.8 >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 18:10:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Bryan Drewery >Release: >Organization: >Environment: >Description: This adds the backports rubygem, which brings Ruby1.9 api changes into Ruby1.8, to help write more portable ruby scripts for 1.9 and have them still work with 1.8. The goal of backports is to make it easier to write ruby code that runs across different versions of Ruby. shar file attached. LICENSE: MIT WWW: https://github.com/marcandre/backports >How-To-Repeat: >Fix: Patch attached with submission follows: # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # rubygem-backports # rubygem-backports/Makefile # rubygem-backports/distinfo # rubygem-backports/pkg-descr # echo c - rubygem-backports mkdir -p rubygem-backports > /dev/null 2>&1 echo x - rubygem-backports/Makefile sed 's/^X//' >rubygem-backports/Makefile << '86fa819e3862bc7324f8ce54efbe0a9e' X# Ports collection makefile for: rubygem-backports X# Date created:24 April 2012 X# Whom:Bryan Drewery X# X# $FreeBSD$ X# X XPORTNAME= backports XPORTVERSION= 2.5.1 XCATEGORIES=devel rubygems XMASTER_SITES= RG X XMAINTAINER=br...@shatow.net XCOMMENT= Ruby 1.9 backports for 1.8 X XLICENSE= MIT X XUSE_RUBY= yes XUSE_RUBYGEMS= yes XRUBYGEM_AUTOPLIST= yes X X.include 86fa819e3862bc7324f8ce54efbe0a9e echo x - rubygem-backports/distinfo sed 's/^X//' >rubygem-backports/distinfo << 'cb3004b829e951d4ffebc3931f193a74' XSHA256 (rubygem/backports-2.5.1.gem) = 6121d3ae1bcffc426db7264bda9ca721270850c125761170ec0764a50eca64db XSIZE (rubygem/backports-2.5.1.gem) = 56320 cb3004b829e951d4ffebc3931f193a74 echo x - rubygem-backports/pkg-descr sed 's/^X//' >rubygem-backports/pkg-descr << '9b22f41a6f0c5b6bf9bf7d69545b562d' XBackports some of the Ruby 1.9 API changes into Ruby 1.8, Xwhich allows for better compatibility between the two versions. X XThe goal of backports is to make it easier to write ruby code Xthat runs across different versions of Ruby. X XWWW: https://github.com/marcandre/backports 9b22f41a6f0c5b6bf9bf7d69545b562d exit >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: ports/167269: New port: devel/rubygem-backports backports ruby 1.9 api changes to 1.8
Synopsis: New port: devel/rubygem-backports backports ruby 1.9 api changes to 1.8 Class-Changed-From-To: sw-bug->change-request Class-Changed-By: ade Class-Changed-When: Tue Apr 24 18:22:47 UTC 2012 Class-Changed-Why: Fix assignment. Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs Responsible-Changed-By: ade Responsible-Changed-When: Tue Apr 24 18:22:47 UTC 2012 Responsible-Changed-Why: Fix assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=167269 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/167272: ZFS Disks reordering causes ZFS to pick the wrong drive
>Number: 167272 >Category: kern >Synopsis: ZFS Disks reordering causes ZFS to pick the wrong drive >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Apr 24 18:50:10 UTC 2012 >Closed-Date: >Last-Modified: >Originator: David Alves >Release:8.2-RELEASE >Organization: >Environment: FreeBSD 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Hello, ZFS shows the disks labels when invoking zpool status, if a disk was removed (physically) and the server rebooted, a reordering of the disks is done, and it appears that the old label is used by a valid disk ( the slot of the removed disks don't contains any new disks) ZFS reports it as follows : raidz2 DEGRADED 0 0 0 da16 ONLINE 0 0 0 da17 ONLINE 0 0 0 da18 ONLINE 0 0 0 da19 ONLINE 0 0 0 da20 ONLINE 0 0 0 da21 OFFLINE 0 0 0 da21 ONLINE 0 0 0 da22 ONLINE 0 0 0 raidz2 DEGRADED 0 0 0 da23 ONLINE 0 0 0 da24 ONLINE 0 0 0 da25 ONLINE 0 0 0 da26 ONLINE 0 0 0 da27 ONLINE 0 0 0 da27 OFFLINE 0 0 0 da29 ONLINE 0 0 0 da30 ONLINE 0 0 0 Notice the da21 and da27 drives. the old disks da21/da27 are shown offline (because they were offlined and removed) but the reordering as assigned those labels to others running drives. The problem is when performing a "zpool replace", "zpool replace" will pick the first label when attempting to replace a disk example when replacing da21: It picked up the da21 offline drive to replace because it was the first on the list. raidz2 DEGRADED 0 0 0 da16 ONLINE 0 0 0 da17 ONLINE 0 0 0 da18 ONLINE 0 0 0 da19 ONLINE 0 0 0 da20 ONLINE 0 0 0 replacing DEGRADED 0 0 0 da21 OFFLINE 0 0 0 da31 ONLINE 0 0 0 37.1G resilvered da21 ONLINE 0 0 0 da22 ONLINE 0 0 1 512 resilvered raidz2 DEGRADED 0 0 0 da23 ONLINE 0 0 0 da24 ONLINE 0 0 0 da25 ONLINE 0 0 0 da26 ONLINE 0 0 0 da27 ONLINE 0 0 0 da27 OFFLINE 0 0 0 da29 ONLINE 0 0 0 da30 ONLINE 0 0 0 example when replacing da27: It picked up the da27 online drive to replace because it was the first on the list. raidz2 ONLINE 0 0 0 da16 ONLINE 0 0 0 da17 ONLINE 0 0 0 da18 ONLINE 0 0 0 da19 ONLINE 0 0 0 da20 ONLINE 0 0 0 da31 ONLINE 0 0 0 da21 ONLINE 0 0 0 da22 ONLINE 0 0 1 raidz2 DEGRADED 0 0 0 da23 ONLINE 0 0 0 da24 ONLINE 0 0 0 da25 ONLINE 0 0 0 da26 ONLINE 0 0 0 replacing ONLINE 0 0 0 da27 ONLINE 0 0 0 da28 ONLINE 0 0 0 80.5G resilvered da27 OFFLINE 0 0 0 da29 ONLINE 0 0 0 da30 ONLINE 0 0 0 That would be nice if we can choose exactly what drive from the pool we are going to replace. Thanks you. >How-To-Repeat: To repeat the problem: offline a drive remove the drive reboot >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/167272: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive
Old Synopsis: ZFS Disks reordering causes ZFS to pick the wrong drive New Synopsis: [zfs] ZFS Disks reordering causes ZFS to pick the wrong drive Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:00:27 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167272 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/167266: [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to NAMEI leak
Old Synopsis: ZFS + new NFS export (sharenfs) leads to NAMEI leak New Synopsis: [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to NAMEI leak Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:01:00 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167266 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/167260: [msdosfs] msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists
Old Synopsis: msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists New Synopsis: [msdosfs] msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 25 05:09:10 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167260 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
