Samba and large files still doesn't work

Hi,
I have ASUS 500g deluxe and have upgraded the firmware to 1.9.2.7-6b from Oleg. I have a 200 Gb usb harddisk on which I have two partitions - ext3 and fat32 (only 1 Gb).
I use Samba with this configuration:

[global]
interfaces = br0
bind interfaces only = yes
workgroup = HOME
guest account = nobody
security = share
browseable = yes
guest ok = yes
guest only = no
log level = 1
max log size = 100
encrypt passwords = no
preserve case = yes
short preserve case = yes

[ext3]
path = /tmp/harddisk
writeable = yes
force user = admin
browseable = yes
[fat32]
path = /tmp/harddisk/part1
writable = yes
force user = admin
browseable = yes

I have no problems with small files such as mp3 music files. I can copy a divx movie file (around 700 Mb) to the ext3 partition but the file gets corrupted - I can't play the file anymore and it doesn't help copying it back to my computer. The file also gets write protected. If I ftp the file to the usb disk there are no problems. Is there something I can do or should I just wait for a new firmware release?
Earlier I had problems with that the ext3 partition got corrupted. To get it working again I just formatted the harddrive but of course that is not a lasting solution. Is there a great tool to repair damaged ext3 partitions?

Best regards,
Kim Therkelsen

I have now used ftp to copy large files to the usb disk but still experience problems. One of my friends was downloading a large file using ftp and after half of it was downloaded the process stopped and the harddisk was inaccessible. The red light on the usb harddisk was on all the time until I rebooted it. After the reboot it worked again.

Best regards,
Kim Therkelsen

Quote:

---

Originally Posted by KimTherkelsen

I have now used ftp to copy large files to the usb disk but still experience problems. One of my friends was downloading a large file using ftp and after half of it was downloaded the process stopped and the harddisk was inaccessible. The red light on the usb harddisk was on all the time until I rebooted it. After the reboot it worked again.

Best regards,
Kim Therkelsen

---

personally I think your drive has a few problems according to your descriptions and behaviours

ftp should work anyway without problems

Perhaps my drive gets too hot, I will try to use it some more and see what happens. I am a little afraid that my ext3 partition will get messed up again though. As I wrote I don't know a Windows tool that can be used to repair an ext3 partition...do you know any?

Best regards,
Kim Therkelsen

telnet to router, unmount all partitions and then run

Code:

---

e2fsck -y partition_name

---

I also have some problems writing on disk. Take a look at your system log:

kernel: I/O error: dev 08:01, sector 34
kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000
kernel: Directory sread (sector 0x7e2) failed
kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:01, sector 2018
kernel: Directory sread (sector 0x7e2) failed

Is that your case?

After this error the filesystem turns into ro mode:

kernel: bread in fat_access failed
kernel: Filesystem panic (dev 08:01).
kernel: fat_free: deleting beyond EOF
kernel: File system has been set read-only
kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:01, sector 2016

Oleg:
Thank you, I will try that the next time it breaks down.

Beci:
Unfortunately I don't have the logs from the crashes anymore but what happened was the the disk either became read only or total unreadable (= the partition was damaged).
I have the log from after a crash and a reboot (all though it guess it not so interesting):

Aug 2 18:19:56 kernel: hub.c: new USB device 01:02.2-2, assigned address 2
Aug 2 18:19:56 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Aug 2 18:20:02 kernel: Vendor: Maxtor 6 Model: B200P0 Rev: 0 0
Aug 2 18:20:02 kernel: Type: Direct-Access ANSI SCSI revision: 02
Aug 2 18:20:02 kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 2 18:20:02 kernel: SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
Aug 2 18:20:02 kernel: Partition check:
Aug 2 18:20:02 kernel: p5 > p2
Aug 2 18:20:10 kernel: attempt to access beyond end of device
Aug 2 18:20:10 kernel: 08:01: rw=0, want=2, limit=1
Aug 2 18:20:10 kernel: EXT3-fs: unable to read superblock
Aug 2 18:20:10 kernel: MSDOS FS: Using codepage 950
Aug 2 18:20:10 kernel: MSDOS FS: IO charset cp950
Aug 2 18:20:10 kernel: FAT: bogus logical sector size 0
Aug 2 18:20:10 kernel: VFS: Can't find a valid FAT filesystem on dev 08:01.
Aug 2 18:20:10 kernel: FAT: freeing iocharset=cp950
Aug 2 18:20:10 kernel: FAT: bogus logical sector size 0
Aug 2 18:20:10 kernel: VFS: Can't find a valid FAT filesystem on dev 08:01.
Aug 2 18:20:11 kernel: kjournald starting. Commit interval 5 seconds
Aug 2 18:20:11 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Aug 2 18:20:11 kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
Aug 2 18:20:11 kernel: EXT3-fs: recovery complete.
Aug 2 18:20:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Aug 2 18:20:11 USB storage: ext3 fs mounted to /tmp/harddisk
Aug 2 18:20:11 kernel: VFS: Can't find ext3 filesystem on dev sd(8,5).
Aug 2 18:20:12 kernel: MSDOS FS: Using codepage 950
Aug 2 18:20:12 kernel: MSDOS FS: IO charset cp950
Aug 2 18:20:12 USB storage: vfat fs mounted to /tmp/harddisk/part1