Date: Tue, 09 Dec 2003 12:49:02 +0200 From: Evren Yurtesen <yurtesen@ispro.net.tr> To: Alex Popa <razor@ldc.ro> Cc: hubs@freebsd.org Subject: Re: Content filtering gone mad on mx1.freebsd.org? Message-ID: <3FD5A89E.4020108@ispro.net.tr> In-Reply-To: <20031208185328.GA96184@ldc.ro> References: <20031208185328.GA96184@ldc.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
I tried to subscribe myself to one freebsd list and my email got rejected. I dont know why. I only had word subscribe I guess I wasnt supposed to send it to the list though? :) Alex Popa wrote: > Attached is a message from one user here in Romania, who is asking if > anyone else is seeing these problems. His mail gets rejected when > sending from two accounts, one on xnet.ro and another one on apropo.ro, > which is webmail. The contents of the message looks OK, and his mail > gets rejected even if he sends just the word "test". > > Thank you > Alex Popa > cvsup.ro.freebsd.org admin > > ------------+------------------------------------------------------- > Alex Popa, | "Computer science is no more about computers than > razor@ldc.ro| astronomy is about telescopes" -- E. W. Dijkstra > ------------+------------------------------------------------------- > > > ------------------------------------------------------------------------ > > Subject: > [rofug] Se mai intampla cuiva ? > From: > Ion-Mihai Tetcu <itetcu@apropo.ro> > Date: > Mon, 8 Dec 2003 16:03:43 +0200 > To: > rofug@rofug.ro > > > De vreo 2 ore nu mai pot sa trimit nimic pe listele @freebsd.org. Si zau > ca n-am schimbat nimic. > > Mai are cineva problema asta ? > > Mesri, > IOnut > > > Begin forwarded message: > > Date: 8 Dec 2003 13:36:35 -0000 > From: MAILER-DAEMON@rdsnet.ro > To: itetcu2@xnet.ro > Subject: failure notice > > > Hi. This is the qmail-send program at rdsnet.ro. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > <freebsd-current@freebsd.org>: > (freebsd-current@freebsd.org) 216.136.204.125 failed after I sent the message. > Remote host said: 550 Error: Message content rejected > > --- Below this line is a copy of the message. > > Return-Path: <itetcu2@xnet.ro> > Received: (qmail 27772 invoked from network); 8 Dec 2003 13:36:26 -0000 > Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) > by mail.rdsnet.ro with SMTP; 8 Dec 2003 13:36:26 -0000 > Date: Mon, 8 Dec 2003 15:37:13 +0200 > From: Ion-Mihai Tetcu <itetcu2@xnet.ro> > To: freebsd-current@freebsd.org, itetcu@apropo.ro > Subject: fsck sig 11 (cannot alloc 4216257920 bytes for inoinfo) > Message-Id: <20031208153713.07056bf6.itetcu2@xnet.ro> > X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) > Mime-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > I've sent the mesage on question with no reply so I'm trying my luck > here. I am able to reproduce both dump/restore and the fsck errors, even > after a fdisk-ing, labeling and newfs-ing (from the sysinstall). > > The nice thing is that everithing seems to be ok (e.g. on new system > install it comes up and run OK) untill the first unclean shutdown, when > fsck complaines about the UNEXPECTED SOFT UPDATE INCONSISTENCY. > > > > Hi, > > > FreeBSD it.buh.cameradicommercio.ro 5.1-RELEASE-p10 FreeBSD > 5.1-RELEASE-p10 #0: Wed Nov 19 00:01:27 EET 2003 > root@it.buh.cameradicommercio.ro:/usr/obj/usr/src/sys/IT1 i386 > > > I was trying to dump/restore my data from my 40G HDD (ad3) on a bigger > 120G HDD (ad0). > > I've booted from the CD, used sysinstall to devide the disk, installed > the minimal distribution, boot up on the new install. Rebooted with the > old system (multiuser but in the console and with no activity beside > dump/restore, with all /usr/local/etc/rc.d stoped), mounted each new > slice and rm -rf * the content. > > dump/restore ad3s2a to ad0s1a (/) > dump/restore ad3s2d to ad0s3d (/tmp) > dump/restore ad3s2e to ad0s1e (/var) > > Untill here everithing OK. > > # mount /dev/ad0s3f /mnt > # mkdir /mnt/home > # mount /dev/ad0s3g /mnt/home > # cd /mnt > # dump 0aLf - / | restore xf - > > Sometime after 1/3 got dumped I've fpund myself in the debbuger with: > /mnt: bad dirino 753722 > panic: ufs_dirbad at offset 0: mangled entry > > I've hit the wrong key so I do not have a core, but I'm confident I can > reproduce if needed. > > Rebooted. After fsck-ing the current disk with good results on the new > disk I get the errors, with fsck saying (complete messages at the end): > for ad0s3f > cannot alloc xxxxxxxxxx bytes for inoinfo > and ending with > fsck_4.2bsd: bad inode number 376832 to nextinode > > for ad0s3g > cannot alloc 4216257920 bytes for inoinfo > UNEXPECTED SOFT UPDATE INCONSISTENCY > UNKNOWN FILE TYPE I=47104 > UNEXPECTED SOFT UPDATE INCONSISTENCY > fsck: /dev/ad0s3g: Segmentation fault > > > ******* Working on device /dev/ad0 ******* > parameters extracted from in-core disklabel are: > cylinders=232578 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=232578 heads=16 sectors/track=63 (1008 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 514017 (250 Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 31/ head 254/ sector 63 > The data for partition 2 is: > sysid 6 (0x06),(Primary 'big' DOS (>= 32MB)) > start 514080, size 41929650 (20473 Meg), flag 0 > beg: cyl 32/ head 0/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 3 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 42443730, size 191992815 (93746 Meg), flag 0 > beg: cyl 1023/ head 255/ sector 63; > end: cyl 1023/ head 254/ sector 63 > The data for partition 4 is: > <UNUSED> > > it# bsdlabel -A /dev/ad0s2c > # /dev/ad0s3c: > type: ESDI > disk: ad0s3 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 14593 > sectors/unit: 234439535 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > b: 2053552 42443730 swap > c: 191992815 42443730 unused 0 0 # "raw" part, don't edit > d: 524288 44497282 4.2BSD 2048 16384 32776 > e: 524288 45021570 4.2BSD 2048 16384 32776 > f: 52428800 45545858 4.2BSD 2048 16384 28552 > g: 136461887 97974658 4.2BSD 2048 16384 28552 > bsdlabel: partition c doesn't start at 0! > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard system utilities > > > it# fsck -n ad0s3g > ** /dev/ad0s3g (NO WRITE) > ** Last Mounted on /mnt/home > ** Phase 1 - Check Blocks and Sizes > cannot alloc 4216257920 bytes for inoinfo > > UNEXPECTED SOFT UPDATE INCONSISTENCY > UNKNOWN FILE TYPE I=47104 > UNEXPECTED SOFT UPDATE INCONSISTENCY > fsck: /dev/ad0s3g: Segmentation fault > > > it# fsck -n ad0s3f > ** /dev/ad0s3f (NO WRITE) > ** Last Mounted on /mnt > ** Phase 1 - Check Blocks and Sizes > cannot alloc 688847944 bytes for inoinfo > > UNEXPECTED SOFT UPDATE INCONSISTENCY > UNKNOWN FILE TYPE I=353280 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=353281 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=353282 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > > [..] > > UNKNOWN FILE TYPE I=376827 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=376828 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=376829 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > PARTIALLY ALLOCATED INODE I=376830 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=376831 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > fsck_4.2bsd: bad inode number 376832 to nextinode > > > Any help will be greatly appreciated. > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-hubs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hubs > To unsubscribe, send any mail to "freebsd-hubs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FD5A89E.4020108>