From owner-freebsd-fs Sun Nov 12 17:48:40 2000 Delivered-To: freebsd-fs@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 306C737B4C5 for ; Sun, 12 Nov 2000 17:48:37 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAD1nj455406 for fs@freebsd.org; Sun, 12 Nov 2000 17:49:45 -0800 (PST) (envelope-from kris) Date: Sun, 12 Nov 2000 17:49:45 -0800 From: Kris Kennaway To: fs@freebsd.org Subject: Non-stat()able directory on msdosfs Message-ID: <20001112174945.A55370@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have a weird directory on an msdos filesystem which appears in the parent directory listing (i.e. ls on the parent directory shows it), but for which stat() on the directory itself fails: mollari# ls . ALL [...] mollari# truss ls ALL ioctl(1,TIOCGETA,0xbfbfef90) = 0 (0x0) ioctl(1,TIOCGWINSZ,0xbfbff004) = 0 (0x0) getuid() = 0 (0x0) readlink("/etc/malloc.conf",0xbfbfeeec,63) ERR#2 'No such file or directory' mmap(0x0,4096,0x3,0x1002,-1,0x0) = 671735808 (0x2809e000) break(0x80b2000) = 0 (0x0) break(0x80b3000) = 0 (0x0) break(0x80b4000) = 0 (0x0) break(0x80b5000) = 0 (0x0) stat("ALL",0xbfbfeeec) ERR#2 'No such file or directory' lstat("ALL",0xbfbfeeec) ERR#2 'No such file or directory' open(".",0,00) = 3 (0x3) ls: write(2,0xbfbfe764,4) = 4 (0x4) ALL: No such file or directorywrite(2,0xbfbfe784,30) = 30 (0x1e) write(2,0xbfbfe764,1) = 1 (0x1) fchdir(0x3) = 0 (0x0) exit(0x1) process exit, rval = 256 This is under 5.0, but I've seen it for quite a while, possibly back as far as pre-4.0. Any ideas? Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoPSLkACgkQWry0BWjoQKXwpQCfaggBwPzGPtLenUgr/auOBnH4 29kAoMvkPYNGknuKzIw+jXMZ3xAAGUTv =wgCR -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Nov 14 21:31:34 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dsl-64-193-123-121.telocity.com (dsl-64-193-123-121.telocity.com [64.193.123.121]) by hub.freebsd.org (Postfix) with ESMTP id 14FB437B4C5 for ; Tue, 14 Nov 2000 21:31:32 -0800 (PST) Received: (from brueggma@localhost) by dsl-64-193-123-121.telocity.com (8.11.1/8.11.1) id eAF5VDP22543; Tue, 14 Nov 2000 23:31:13 -0600 (CST) (envelope-from brueggma) Date: Tue, 14 Nov 2000 23:31:12 -0600 From: Eric Brueggmann To: bp@butya.kz Cc: freebsd-fs@freebsd.org Subject: smbfs-1.3.1 Message-ID: <20001114233112.A21938@snoopie.yi.org> Reply-To: brueggma@snoopie.yi.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I seem to be having some more problems with smbfs. I'm using smbfs to backup filesystems to a WinME box. And yesterday the dump just hung, allong with certain commands: # ps axuw | grep quota mircsux 52150 0.0 0.1 912 248 p3- D 4:09AM 0:00.01 quota Rupture 92852 0.0 0.1 908 280 p2- D 3:58PM 0:00.01 quota Rupture 93766 0.0 0.1 908 288 p2- D 4:13PM 0:00.01 quota steve 98850 0.0 0.1 908 288 p2- D 5:47PM 0:00.01 quota steve 99240 0.0 0.1 908 288 p2- D 5:52PM 0:00.01 quota barkerjr 99739 0.0 0.1 908 288 pa- D 6:01PM 0:00.01 quota barkerjr 99851 0.0 0.1 908 288 pa- D 6:03PM 0:00.01 quota barkerjr 9879 0.0 0.2 908 456 pa- D 8:02PM 0:00.01 quota giemsboy 17145 0.0 0.2 908 460 p3- D 9:59PM 0:00.01 quota giemsboy 18152 0.0 0.2 908 460 p3- D 10:14PM 0:00.01 quota root 22082 0.0 0.2 1048 536 p9 S+ 11:23PM 0:00.01 grep quota # ps axuw | grep df root 21173 0.0 0.0 208 68 p2- D 11:09PM 0:00.00 df The FreeBSD box dosen't reboot, hang, drop core or show anyother kinds of problems that I'm aware of. What could be the problem? Eric Brueggmann # uname -a FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 27 02:31:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 15 2: 7:44 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id DC85A37B479 for ; Wed, 15 Nov 2000 02:07:41 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id ED2E62874E; Wed, 15 Nov 2000 16:07:37 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id DE7DC2874C; Wed, 15 Nov 2000 16:07:37 +0600 (ALMT) Date: Wed, 15 Nov 2000 16:07:37 +0600 (ALMT) From: Boris Popov To: Eric Brueggmann Cc: freebsd-fs@freebsd.org Subject: Re: smbfs-1.3.1 In-Reply-To: <20001114233112.A21938@snoopie.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 14 Nov 2000, Eric Brueggmann wrote: > I seem to be having some more problems with smbfs. I'm using > smbfs to backup filesystems to a WinME box. And yesterday the dump just > hung, allong with certain commands: Output of 'ps axl' command should give a state on which these commands hung. Looks like some kind of dead lock occured. btw, 1.3.1 contains a nasty bug which appears when USE_ICONV set to 'yes'. This weekend I'll release 1.3.2 with this and some other non-critical bugfixes. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 15 9:58:59 2000 Delivered-To: freebsd-fs@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id C83EE37B479 for ; Wed, 15 Nov 2000 09:58:57 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id KAA10944; Wed, 15 Nov 2000 10:59:31 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAA9JaOmv; Wed Nov 15 10:59:16 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id KAA13857; Wed, 15 Nov 2000 10:58:36 -0700 (MST) From: Terry Lambert Message-Id: <200011151758.KAA13857@usr01.primenet.com> Subject: Re: smbfs-1.3.1 To: brueggma@snoopie.yi.org Date: Wed, 15 Nov 2000 17:58:36 +0000 (GMT) Cc: bp@butya.kz, freebsd-fs@FreeBSD.ORG In-Reply-To: <20001114233112.A21938@snoopie.yi.org> from "Eric Brueggmann" at Nov 14, 2000 11:31:12 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I seem to be having some more problems with smbfs. I'm using > smbfs to backup filesystems to a WinME box. And yesterday the dump just > hung, allong with certain commands: You should probably turn of quota processing. The SMBFS code does not support quotas. This is probably a misimplementation of the default quota processing entry point(s) for the SMBFS, since this should never happen when calling quota processing on an FS not supporting quotas. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 15 20:45:48 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id B47B437B479 for ; Wed, 15 Nov 2000 20:45:45 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 7650428DBB; Thu, 16 Nov 2000 10:45:43 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 6D76328A25; Thu, 16 Nov 2000 10:45:43 +0600 (ALMT) Date: Thu, 16 Nov 2000 10:45:43 +0600 (ALMT) From: Boris Popov To: Terry Lambert Cc: brueggma@snoopie.yi.org, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.1 In-Reply-To: <200011151758.KAA13857@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 15 Nov 2000, Terry Lambert wrote: > > I seem to be having some more problems with smbfs. I'm using > > smbfs to backup filesystems to a WinME box. And yesterday the dump just > > hung, allong with certain commands: > > You should probably turn of quota processing. The SMBFS code > does not support quotas. This is probably a misimplementation > of the default quota processing entry point(s) for the SMBFS, > since this should never happen when calling quota processing > on an FS not supporting quotas. SMBFS returns EOPNOTSUPP for quotactl operation. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Nov 16 0:34:43 2000 Delivered-To: freebsd-fs@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 8173E37B479 for ; Thu, 16 Nov 2000 00:34:41 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id BAA13682; Thu, 16 Nov 2000 01:35:08 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp05.primenet.com, id smtpdAAAzNaaTA; Thu Nov 16 01:35:04 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA01079; Thu, 16 Nov 2000 01:34:23 -0700 (MST) From: Terry Lambert Message-Id: <200011160834.BAA01079@usr02.primenet.com> Subject: Re: smbfs-1.3.1 To: bp@butya.kz (Boris Popov) Date: Thu, 16 Nov 2000 08:34:22 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), brueggma@snoopie.yi.org, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Boris Popov" at Nov 16, 2000 10:45:43 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I seem to be having some more problems with smbfs. I'm using > > > smbfs to backup filesystems to a WinME box. And yesterday the dump just > > > hung, allong with certain commands: > > > > You should probably turn of quota processing. The SMBFS code > > does not support quotas. This is probably a misimplementation > > of the default quota processing entry point(s) for the SMBFS, > > since this should never happen when calling quota processing > > on an FS not supporting quotas. > > SMBFS returns EOPNOTSUPP for quotactl operation. Then it must put the string "quota" in where it's not appropriate, for it to show up in the wait channel list of so many users in the bug being reported, I guess? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Nov 18 22:11:17 2000 Delivered-To: freebsd-fs@freebsd.org Received: from modgud.nordicrecords.com (h21-168-107.nordicdms.com [207.21.168.107]) by hub.freebsd.org (Postfix) with SMTP id 6B2E737B479 for ; Sat, 18 Nov 2000 22:11:12 -0800 (PST) Received: (qmail 5711 invoked by alias); 19 Nov 2000 06:11:11 -0000 Received: (qmail 5704 invoked from network); 19 Nov 2000 06:11:10 -0000 Received: from adsl-216-103-90-137.dsl.snfc21.pacbell.net (HELO thinkpad770z) (216.103.90.137) by mail.nordicrecords.com with SMTP; 19 Nov 2000 06:11:10 -0000 From: "Dave Walton" To: fs@freebsd.org Date: Sat, 18 Nov 2000 22:10:57 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: corrupted filesystem Reply-To: dwalton@acm.org Message-ID: <3A16FE71.20481.69FB69@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Boy have I got a stinker of a mess. A server crashed, apparently due to a power supply problem, and messed up its filesystem pretty thoroughly. I need some help digging through the piles of bits. (As an aside, I'd had the notion that only open files were at risk for corruption. These problems seem more widespread than that. Why might that be? Would softupdates have prevented the problem?) Anyway, I ran fsck -n to have a peek, and it ran for a couple of hours before I killed it, spewing an incredible number of problem reports. I am reluctant to use fsck -y for fear that it would cause even more data loss, and answering all those questions manually is right out. This is an 85GB filesystem. It'd take forever, even if I did know the "right" answers. What I'd really like to do is just rescue as much as I can from /usr/home, then clean up the rest of the mess with newfs. To that end, I mounted the /usr filesystem read only on /mnt and started poking around. Right off the bat I ran into this: ------------------------------------------------------------ /mnt# ls -alF ls: libdata: Bad file descriptor ls: local: Bad file descriptor ls: share: Bad file descriptor ls: src: Bad file descriptor total 1235043903 drwxr-xr-x 17 root wheel 512 Aug 24 23:45 ./ drwxr-xr-x 15 root wheel 512 Nov 18 02:29 ../ drwxr-xr-x 2 root wheel 6656 Aug 25 06:07 bin/ drwxr-xr-x 3 root wheel 512 Aug 23 19:17 compat/ drwxr-xr-x 3 root wheel 1024 Aug 23 18:26 games/ -rws-w--wx 32458 389421524 3725029886 7966077931114349813 Jan 30 2022 home* drwxr-xr-x 35 root wheel 3072 Aug 24 05:55 include/ drwxr-xr-x 4 root wheel 6656 Aug 24 05:57 lib/ drwxr-xr-x 8 root wheel 1024 Aug 24 05:57 libexec/ drwxr-xr-x 3 root wheel 512 Aug 24 23:57 obj/ drwxr-xr-x 51 root wheel 1024 Aug 23 18:47 ports/ -rw-r----- 1 root operator 2097120 Nov 17 04:23 quota.group -rw-r----- 1 root operator 2097120 Nov 17 04:23 quota.user drwxr-xr-x 2 root wheel 4096 Aug 25 06:07 sbin/ drwxrwxrwt 3 root wheel 1536 Nov 16 10:08 tmp/ /mnt# ------------------------------------------------------------ By some magic, home has become a regular file instead of a dir! Well, that won't do at all, because that is the place I most need to get to. So I gritted my teeth and fired up fsdb (first time ever) to have a look-see: ------------------------------------------------------------ /# fsdb -r /dev/rda0s1f ** /dev/rda0s1f (NO WRITE) Examining file system `/dev/rda0s1f' Last Mounted on /usr current inode: directory I=2 MODE=40755 SIZE=512 MTIME=Aug 24 23:45:30 2000 [0 nsec] CTIME=Aug 24 23:45:30 2000 [0 nsec] ATIME=Nov 17 00:25:04 2000 [0 nsec] OWNER=root GRP=wheel LINKCNT=17 FLAGS=0 BLKCNT=2 GEN=6f7bd28 fsdb (inum: 2)> ls slot 0 ino 2 reclen 12: directory, `.' slot 1 ino 2 reclen 12: directory, `..' slot 2 ino 7936 reclen 12: directory, `bin' slot 3 ino 15872 reclen 16: directory, `include' slot 4 ino 349184 reclen 12: directory, `lib' slot 5 ino 380928 reclen 16: directory, `libdata' slot 6 ino 1190400 reclen 16: directory, `libexec' slot 7 ino 1253888 reclen 16: directory, `local' slot 8 ino 1261824 reclen 16: directory, `sbin' slot 9 ino 1269760 reclen 16: directory, `share' slot 10 ino 3222016 reclen 12: directory, `src' slot 11 ino 4063232 reclen 16: directory, `games' slot 12 ino 1222148 reclen 16: directory, `ports' slot 13 ino 15014935 reclen 16: directory, `compat' slot 14 ino 15038738 reclen 12: directory, `obj' slot 15 ino 15443479 reclen 12: directory, `tmp' slot 16 ino 3039518 reclen 16: directory, `home' slot 17 ino 27 reclen 20: regular, `quota.user' slot 18 ino 28 reclen 248: regular, `quota.group' fsdb (inum: 2)> cd home component `home': current inode: regular file I=3039518 MODE=104723 SIZE=7966077931114349813 MTIME=Jan 30 19:02:03 2022 [2140389655 nsec] CTIME=Nov 2 18:02:35 1975 [-556098662 nsec] ATIME=Feb 7 04:40:01 2016 [374691499 nsec] OWNUID=389421524 GID=3725029886 LINKCNT=32458 FLAGS=0xb03ec3e0 BLKCNT=933a8bb1 GEN=7f060afc fsdb (inum: 3039518)> ------------------------------------------------------------ Ok, now I'm really confused! First fsdb reports home as a directory, but when I cd into it, it becomes a regular file? How can that be? So that's where I am. Any suggestions for getting into home are most welcome. I have the feeling that home itself may be a lost cause. How can I search for all directories that had home as a parent and relink them somewhere else? Any other ideas? In summary.... HELP! :) Thanks for listening, Dave ---------------------------------------------------------------------- Dave Walton dwalton@acm.org ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message