Messages in this thread |  | | | Date | Thu, 06 Aug 1998 17:54:13 +0100 (GMT+0100) | | From | Magnus & Tina <> | | Subject | ext2 corruption?? |
| |
I have a problem with one of my disks. I can't get back part of the unused space no matter how I try. The /dev/sdb1 is never up to date.
I boot the /redhat as root and then e2fsck /dev/sdb1, mount it, unmount it ... Nothing helps. There is currently a difference of 102814. Is this the way it should be?
Kernel 2.1.113 and ext2fstools 1.12.
Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sdb1 1988924 1856767 29343 98% / /dev/scd0 368230 368230 0 100% /cdrom /dev/sda2 389936 384000 5936 98% /dosc /dev/sdb4 1019856 815888 203968 80% /dosd /dev/sdd2 2096192 1215232 880960 58% /dose /dev/sdb5 1052064 1030272 21792 98% /dosf /dev/sda5 314231 184711 113291 62% /opt/kde /dev/sdc2 2046244 82140 1858480 4% /usr/src /dev/md0 4098127 510325 3375748 13% /redhat
(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 12/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) BIOS enabled, IO Port 0xe000, IRQ 9 (scsi0) IO Memory at 0xf9000000, MMAP Memory at 0xc4945000 (scsi0) Downloading sequencer code... 413 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.19/3.2.4 <Adaptec AHA-294X Ultra SCSI host adapter> scsi : 1 host. (scsi0:0:-1:-1) Scanning channel for devices. Vendor: QUANTUM Model: LIGHTNING 730S Rev: 241E Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 Vendor: QUANTUM Model: XP34301 Rev: 1071 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0 Vendor: TEAC Model: CD-R55S Rev: 1.0H Type: CD-ROM ANSI SCSI revision: 02 Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Vendor: IBM Model: DCAS-34330W Rev: S65A Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdc at scsi0, channel 0, id 5, lun 0 Vendor: IBM Model: DCAS-34330W Rev: S65A Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdd at scsi0, channel 0, id 6, lun 0 scsi : detected 1 SCSI cdrom 4 SCSI disks total. (scsi0:0:3:0) Synchronous at 10.0MHz, offset 15. Uniform CDROM driver Revision: 2.13 (scsi0:0:1:0) Synchronous at 10.0MHz, offset 8. SCSI device sda: hdwr sector= 512 bytes. Sectors= 1431760 [699 MB] [0.7 GB] (scsi0:0:2:0) Using wide (16 bit) transfers. (scsi0:0:2:0) Synchronous at 10.0MHz, offset 8. SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8410200 [4106 MB] [4.1 GB] (scsi0:0:5:0) Using wide (16 bit) transfers. (scsi0:0:5:0) Synchronous at 20.0MHz, offset 8. SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB] (scsi0:0:6:0) Using wide (16 bit) transfers. (scsi0:0:6:0) Synchronous at 20.0MHz, offset 8. SCSI device sdd: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB] Partition check: sda: sda1 < sda5 > sda2 sdb: sdb1 sdb2 sdb3 < sdb5 > sdb4 sdc: sdc1 sdc2 sdd: sdd1 sdd2 On 05-Aug-98 Theodore Y. Ts'o wrote: > Date: Wed, 05 Aug 1998 11:29:34 +0300 > From: "Ville =?ISO-8859-1?Q?P=E4tsi" ?= <NOSPAMdrc@zoo-gate.fi> > > s-----xrwx 1 65535 65535 4294967295 Jul 3 1969 Makefile.in > > That file appeared during the time i realised my /ext drive was > corrupted. Apparently the cause for corruption was doing compilation, > rm and df at the same time on that drive. > > That's bad; can you report on what your hardware was? This sort of > thing shouldn't be happening, and to date many of the problems where > chalked up to hardware problems or the DMA problem that a few people > where having. > > Hmm... actually given the values 65535 and 429496729 (0xFFFF and > 0xFFFFFFFF, respectively), my guess was this was a hardware problem that > scribbed all ones on a part of your inode table. > > E2fsck fixed the drive but left this file there. > > Oops. In 1.12 I fixed the problem for character and block devices > (which were the most commonly reported case), but I forgot to fix it for > Unix-domain socket files. I'll get this fixed in the next release. > > In the meantime, you're going to have to fix this by using the debugfs's > clri command. Make sure you do this with the filesystem unmounted; run > the command "debugfs -w /dev/XXXX", then use the cd and ls commands to > find the appropriate file. You can them remove it using the clri > command; then quit debugfs and make sure you run e2fsck on the device > before you remount the drive. > > Sorry for the inconvenience. > > - Ted > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
.---. .----------- Magnus Back / \ __ / ------ Nippon Ericsson K.K / / \( )/ ----- SY/NRJ/SV/F MBK ////// ' \/ ` --- Magnus.Back@ericsson.co.jp (work) //// / // : : --- magnus@gol.com (home) // / / /` '-- +81-45-475-0418 phone // //..\\ +81-45-475-0040 fax ====UU====UU==== http://www2.gol.com/users/magnus/ '//||\\` ''`` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
|  |