Date: Fri, 6 Mar 1998 03:49:49 -0300 (EST) From: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br> To: jonny@coppe.ufrj.br (jonny) Cc: hackers@FreeBSD.ORG Subject: Re (Solved) dump bug or file system problem ? Message-ID: <199803060649.DAA13889@gaia.coppe.ufrj.br> In-Reply-To: From jonny at "Mar 4, 98 03:57:51 pm"
next in thread | raw e-mail | index | archive | help
Answering myself, I think I found the problem. I had a bad hardware for some time (motherboard), and the system was frequently panicing. I have even once to remove an inode manually (clri), for fsck could not fix the file system. Now I found this: gaia::jonny [521] ls -lisa /usr/bin/ranlib 8050 16 -r-xr-xr-x 1 bin bin 1125899906859008 Feb 16 16:58 /usr/bin/ranlib I am really amazed that ls could even list a file with this size. :) But dump could not, and gave me that negative numbers. (Should we have a 64 bit aware dump now ? :) ). #define quoting(jonny) // Hi, // // I've sent this to -questions (and got no answer), but after reading // the sources of dump, I think it's more a -hackers question. // // I'm right now trying to make a dump of my file system, but it seems // to never end (dumping to /dev/null to make sure it's not a tape // problem): // // gaia::jonny [503] dump 0fa /dev/null /usr // DUMP: Date of this level 0 dump: Wed Mar 4 13:57:54 1998 // DUMP: Date of last level 0 dump: the epoch // DUMP: Dumping /dev/rsd0f (/usr) to /dev/null // DUMP: mapping (Pass I) [regular files] // DUMP: mapping (Pass II) [directories] // DUMP: estimated 1545215 tape blocks. // DUMP: dumping (Pass III) [directories] // DUMP: 27.30% done, finished in 0:13 // DUMP: 57.87% done, finished in 0:07 // DUMP: 88.27% done, finished in 0:01 // DUMP: 119.27% done, finished in 0:-3 // DUMP: 148.05% done, finished in 0:-8 // DUMP: 176.90% done, finished in 0:-13 // DUMP: 208.32% done, finished in 0:-18 // DUMP: 240.57% done, finished in 0:-23 // DUMP: 270.01% done, finished in 0:-28 // DUMP: 300.63% done, finished in 0:-33 // DUMP: 332.25% done, finished in 0:-38 // DUMP: 363.33% done, finished in 0:-43 // DUMP: 393.50% done, finished in 0:-48 // DUMP: 418.82% done, finished in 0:-53 // DUMP: 445.49% done, finished in 0:-58 // DUMP: 473.04% done, finished in -1:-3 // DUMP: 502.15% done, finished in -1:-8 // DUMP: 530.49% done, finished in -1:-13 // DUMP: 558.39% done, finished in -1:-17 // (and continues...) // // The first think I thought was a problem with integer length in dump, // but I've never had this before and could not find a problem like that // in dump sources. It seems to be able to handle file systems with 2^41 // bytes, and that is definitely not my case. And not all of them beeing // directories. // // Other possibility is a file system problem. I've had problems with // it in the last weeks, with panic "freeing a free frag" or something // like that. At this time, fsck finds no error, though. // // I would love any hint that could help me solving this problem. This // is what df reports on this file system: // // Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on // /dev/sd0f 1822017 1486754 189502 89% 70480 374958 16% /usr // // Thanks in advance, // // Jonny // // -- // Joao Carlos Mendes Luis jonny@gta.ufrj.br // +55 21 290-4698 jonny@coppe.ufrj.br // Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI // PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 // Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803060649.DAA13889>