Re: IBM TSM server
On Sun, Jun 7, 2009 at 11:26 PM, Miroslav Lachman 000.f...@quip.cz wrote: claudiu vasadi wrote: On Sun, Jun 7, 2009 at 9:38 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: Jun 7 21:10:47 da1 kernel: ad6: detached Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86540058624, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1e[READ(offset=63203147776, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86539010048, length=16384)]error = 6 isn;t it trying to read past the end of disk? Hmm.. I guess you are correct. The question is why is it doing this ? It can be caused by wrong disk label (partitioning). Some partition made bigger then real media [disk]. You can see the label by command disklabel ad6s1 and then compare size offset values with `diskinfo -v ad6` Here is the ad2: [...@da1.ro /home/da1]# disklabel ad2s1 # /dev/ad2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 4125328 1048576 swap c: 419295870unused0 0 # raw part, don't edit d: 4159488 51739044.2BSD 2048 16384 28552 e: 1048576 9924.2BSD 2048 16384 8 f: 31547619 103819684.2BSD 2048 16384 28552 [...@da1.ro /home/da1]# diskinfo -v ad2 ad2 512 # sectorsize 80060424192 # mediasize in bytes (75G) 156368016 # mediasize in sectors 155127 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:S00JJ30X533937 # Disk ident. And the ad6: [...@da1.ro /home/da1]# disklabel ad6s1 # /dev/ad6s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 4902234120unused0 0 # raw part, don't edit d: 25165824004.2BSD0 0 0 e: 167772160 2516582404.2BSD0 0 0 f: 70793012 4194304004.2BSD0 0 0 [...@da1.ro /home/da1]# diskinfo -v ad6 ad6 512 # sectorsize 251000193024# mediasize in bytes (234G) 490234752 # mediasize in sectors 486344 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:WD-WCANY2281832 # Disk ident. [...@da1.ro /home/da1]# ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IBM TSM server
isn;t it trying to read past the end of disk? Hmm.. I guess you are correct. The question is why is it doing this ? because partition/slice table is wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IBM TSM server
On Mon, Jun 8, 2009 at 9:16 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: the type fdisk /dev/da1 and then compare the sectors values with what dmesg says fdisk /dev/ad2 : *** Working on device /dev/ad2 *** parameters extracted from in-core disklabel are: cylinders=155127 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=155127 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 41929587 (20473 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 41929650, size 114430995 (55874 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 dmesg doesn't say anything usefull. only: ad2: 76351MB SAMSUNG SP0802N TK200-04 at ata1-master UDMA100 I'm not pretty good at this but it seams ok. the disk has been 99% full before and no problems. The slices were created a long time ago and ran some random test that all came out ok. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
IBM TSM server
Hello again. About a week ago I cryed on your shoulders but since no one is answering I am crying again. This time with more accurate data. My sistem is a P4 2.66 Mhz (sk 478) Intel P4 processor with 1 GB DDR1 ram, mobo Asus p4p800-x with 2 HDD's. One of them (ad2 ) is a Samsing SpinPoint of 80GB ATA and is the one used by the actual OS. The second one (ad6) is a WD 250 GB S-ATA2 and has some data on it. The server acts as a web server, ftp server, NAS, samba svr, a p2p server (verlihub) and just about every normal app a mental deranged person can have running :P (those kind that dnt have money to buy the ultra ultimate bullshit in hardware or more than two 2 pc's. Leaving this asside here is my situation. Ups, almost forgot. I have a FreeBSD-7.0-STABLE. I have a Windows machine with vmware and solaris on it. In solaris there is a IBM TSM (Tape Storage Management) Server. The server can use disks over tapes to build pools. So I added the local windows disks, and have some 30 G of free space on freebsd, so I thought, I would add them to the storage pool. There's my mistake ... thinking :P Every time I try to add that space to the storage pool the system crashes with a kernel panic. Here is the /var/log/messages file Jun 7 21:03:45 da1 fsck: /dev/ad6s1d: INCORRECT BLOCK COUNT I=5652481 (0 should be 4) (CORRECTED) Jun 7 21:03:45 da1 fsck: /dev/ad6s1d: 16137 files, 45577224 used, 15357050 free (2210 frags, 1919355 blocks, 0.0% fragmentation) Jun 7 21:10:47 da1 syslogd: kernel boot file is /boot/kernel/kernel Jun 7 21:10:47 da1 kernel: ad6: FAILURE - device detached Jun 7 21:10:47 da1 kernel: subdisk6: detached Jun 7 21:10:47 da1 kernel: ad6: detached Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86540058624, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1e[READ(offset=63203147776, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86539010048, length=16384)]error = 6 [...] [...] [...] Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=46438858752, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=46252277760, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: panic: vinvalbuf: dirty bufs Jun 7 21:10:47 da1 kernel: cpuid = 0 Jun 7 21:10:47 da1 kernel: Uptime: 21m50s Jun 7 21:10:47 da1 kernel: Physical memory: 1011 MB So I'm guesing the script that adds the space to the pool is doing some crap. I tryed using both HDD's but the result is the same - sistem crash. I have no kernel dump file defined yet (dnt ask why, I've setted up long ago but for some reason this time it didn't write to it) . REPRODUCE: The only way to reproduce the problem is by telling tsm server to add the available 30G off free space. What the tsm server doesm, is it creates a file of a given size, in this case 25G out of the total of 30G, and then populates the file with whatever data it is given as backup data. I really have no ideea if this is the right mailing list for this matter. If it is not, please advise in this matter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IBM TSM server
Jun 7 21:10:47 da1 kernel: ad6: detached Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86540058624, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1e[READ(offset=63203147776, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86539010048, length=16384)]error = 6 isn;t it trying to read past the end of disk? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IBM TSM server
On Sun, Jun 7, 2009 at 9:38 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: Jun 7 21:10:47 da1 kernel: ad6: detached Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86540058624, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1e[READ(offset=63203147776, length=16384)]error = 6 Jun 7 21:10:47 da1 kernel: g_vfs_done():ad6s1d[READ(offset=86539010048, length=16384)]error = 6 isn;t it trying to read past the end of disk? Hmm.. I guess you are correct. The question is why is it doing this ? And on both drives ? Feels to me a problem for the developers. HDD's didn't give me one problem since the day the got installed. I'm not saing that they are very good HDD's (in fact they are quite cheap ones) but fail all of a sudden ? And leaving this asside, they dnt give one error on masive transfers and still have very good transfer speed. What I'm saing is that hdd failure could be a posibility of course, but a unlikely one at this point. My problem is that I do not know what tehnik TSM server uses for creating those files because at some point it fails. Strainge thing is that it goes over 1G. First it creates the file and then it populates the file up until the given limit (25G in this case). I will try something tomorow. I will again start the tsm server to add the space (the 25G free space) to the pool and will monitor the file size up until the OS crashes. I'm very curious what's the size of the file when the OS crashes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
