2010-05-04 10:32:49     FAT: Directory bread(block 7738) failed

Document created by Aaronwu Employee on Aug 21, 2013
Version 1Show Document
  • View in full screen mode

2010-05-04 10:32:49     FAT: Directory bread(block 7738) failed

John Peter (INDIA)

Message: 89113   

 

Hai,

I have enabled hotplug for detecting USB in the kernel. I have a USB hard disc having about 10 partitions of which 8 are mountable. In my application I browsed the content of one partition and removed the USB hard disc. When I reattached the USB hard disc I am getting the following error. Can you please figure out where to check for this one? But this is not happening for a normal USB . Only for multi partition USB hard disc I am getting this error.

 

The current Page Index is : 0

>>1. Folder1            DIR

  2. Folder1 (1)                DIR

  3. Folder1 (2)                DIR

 

Enter the Page Index for Browsing : usb 1-2: USB disconnect, address 5

hotplug: usb removed

586     CheckUSB

588     CheckUSB

USB Removed...!

usb 1-2: new high speed USB device using r8a66597_hcd and address 6

usb 1-2: configuration #1 chosen from 1 choice

scsi3 : SCSI emulation for USB Mass Storage devices

usb 1-2: New USB device found, idVendor=1058, idProduct=0704

usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

usb 1-2: Product: External HDD

usb 1-2: Manufacturer: Western Digital

usb 1-2: SerialNumber: 57442D575832304135393730393133

usb 1-2: address 6, EndpointAddress 0x02 use DMA FIFO

usb 1-2: address 6, EndpointAddress 0x81 use DMA FIFO

scsi 3:0:0:0: Direct-Access     WD       2500BEV External 1.75 PQ: 0 ANSI: 4

sd 3:0:0:0: [sdd] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 3:0:0:0: [sdd] Write Protect is off

sd 3:0:0:0: [sdd] Assuming drive cache: write through

sd 3:0:0:0: [sdd] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 3:0:0:0: [sdd] Write Protect is off

sd 3:0:0:0: [sdd] Assuming drive cache: write through

sdd: sdd1 < sdd5 sdd6 sdd7 sdd8 sdd9 sdd10 sdd11 sdd12 >

sd 3:0:0:0: [sdd] Attached SCSI disk

hotplug: usb inserted

hotplug: usb inserted

hotplug: usb inserted

597     CheckUSB

hotplug: usb inserted

hotplug: usb inserted

142     USB_Mount

au8_SDBBLock[2] is sdd5

au8_SDBBLock[3] is sdd6

au8_SDBBLock[4] is sdd7

au8_SDBBLock[5] is sdd8

au8_SDBBLock[6] is sdd9

au8_SDBBLock[7] is sdd10

au8_SDBBLock[8] is sdd11

au8_SDBBLock[9] iFAsdT:2 Directory bread(block 7736) failed

 

7) failedD32iroOecLotos ry 8 b18re      Uad_M(bntlo60ck C 7ck73B

FAT: Directory bread(block 7738) failed

FAT: Directory bread(block 7739) failed

FAT: Directory bread(block 7740) failed

FAT: Directory bread(block 7741) failed

FAT: Directory bread(block 7742) failed

FAT: Directory bread(block 7743) failed

 

Thanks,

Peter

QuoteReplyEditDelete

 

 

2010-05-04 13:58:38     Re: FAT: Directory bread(block 7738) failed

Mike Frysinger (UNITED STATES)

Message: 89122   

 

please search the forums.  you can never safely unplug a device while partitions are mounted.  this is expected behavior after user error.

QuoteReplyEditDelete

 

 

2010-05-05 01:35:09     Re: FAT: Directory bread(block 7738) failed

John Peter (INDIA)

Message: 89140   

 

Hai Mike,

 

                   Thanks for your support. I will take care of  "FAT: Directory bread(block 7738) failed" in my application. But I am getting kernel panic sometimes which is shown below. Can you please clarify this?

 

Entering the Path:/mnt/3...

Total Record Count : 20

The current Page Index is : 2

>>1. ENNAVALAE _ KADHALAN.MP3           FILE

  2. Girl Friend - Karthik  Timmy  Tipu.mp3             FILE

  3. KAADHAL_ROJAVE.MP3         FILE

  4. KAADU POTTA _ KARUTHAMMA.mp3               FILE

 

Enter the Page Index for Browsing : usb 1-2: USB disconnect, address 9

hotplug: usb removed

hotplug: usb removed

hotplug: usb removed

hotplug: usb removed

hotplug: usb removed

589     CheckUSB

591     CheckUSB

USB Removed...!

usb 1-2: new high speed USB device using r8a66597_hcd and address 10

usb 1-2: configuration #1 chosen from 1 choice

scsi7 : SCSI emulation for USB Mass Storage devices

usb 1-2: New USB device found, idVendor=1058, idProduct=0704

usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

usb 1-2: Product: External HDD

usb 1-2: Manufacturer: Western Digital

usb 1-2: SerialNumber: 57442D575832304135393730393133

usb 1-2: address 10, EndpointAddress 0x02 use DMA FIFO

usb 1-2: address 10, EndpointAddress 0x81 use DMA FIFO

scsi 7:0:0:0: Direct-Access     WD       2500BEV External 1.75 PQ: 0 ANSI: 4

sd 7:0:0:0: [sde] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 7:0:0:0: [sde] Write Protect is off

sd 7:0:0:0: [sde] Assuming drive cache: write through

sd 7:0:0:0: [sde] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 7:0:0:0: [sde] Write Protect is off

sd 7:0:0:0: [sde] Assuming drive cache: write through

sde: sde1 < sde5 sde6 sde7 sde8 sde9 sde10 sde11 sde12 >

sd 7:0:0:0: [sde] Attached SCSI disk

hotplug: usb inserted

Hardware Trace:

   0 Target : <0x00183838> { _dump_bfin_trace_buffer + 0x0 }

     Source : <0x001bae34> { _cache_alloc_refill + 0x194 } CALL pcrel

   1 Target : <0x001bae34> { _cache_alloc_refill + 0x194 }

     Source : <0x001bad20> { _cache_alloc_refill + 0x80 } IF !CC JUMP

   2 Target : <0x001bad0c> { _cache_alloc_refill + 0x6c }

     Source : <0x001bad90> { _cache_alloc_refill + 0xf0 } IF CC JUMP

   3 Target : <0x001bad8e> { _cache_alloc_refill + 0xee }

     Source : <0x001bae06> { _cache_alloc_refill + 0x166 } JUMP.S

   4 Target : <0x001badf8> { _cache_alloc_refill + 0x158 }

     Source : <0x001bad7c> { _cache_alloc_refill + 0xdc } IF !CC JUMP

   5 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

   6 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

   7 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

   8 Target : <0x001bad38> { _cache_alloc_refill + 0x98 }

     Source : <0x001bad2c> { _cache_alloc_refill + 0x8c } JUMP.S

   9 Target : <0x001bad0c> { _cache_alloc_refill + 0x6c }

     Source : <0x001bad90> { _cache_alloc_refill + 0xf0 } IF CC JUMP

  10 Target : <0x001bad8e> { _cache_alloc_refill + 0xee }

     Source : <0x001bae06> { _cache_alloc_refill + 0x166 } JUMP.S

  11 Target : <0x001badf8> { _cache_alloc_refill + 0x158 }

     Source : <0x001bad7c> { _cache_alloc_refill + 0xdc } IF !CC JUMP

  12 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

  13 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

  14 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

  15 Target : <0x001bad2e> { _cache_alloc_refill + 0x8e }

     Source : <0x001bad5e> { _cache_alloc_refill + 0xbe } IF CC JUMP

BUG: failure at mm/slab.c:3000/cache_alloc_refill()!

Kernel panic - not syncing: BUG!

 

Thanks,

 

Peter

QuoteReplyEditDelete

 

 

2010-05-05 01:47:11     Re: FAT: Directory bread(block 7738) failed

Mike Frysinger (UNITED STATES)

Message: 89141   

 

no idea.  does it only crash with a corrupted fs ?  does it ever crash with a non-corrupt fs ?  run dosfsck on the fs to fix it.

 

perhaps the linux experts at jasmin might be able to help

Attachments

    Outcomes