NSLU2 SAMBA bug?

Discussion in 'Cisco/Linksys Network Storage Devices' started by PedrosPad, Oct 12, 2005.

  1. PedrosPad

    PedrosPad Network Guru Member

    The other night I was using a WinXP machine and moving a bunch of folders between the two hard disks connected to the NSLU2. The source one was ext3 format, and the destination FAT32. These were large files - 650MB CD-Rom ISO images.

    After I’d initiated the movement of a large group of folders, and after a few of them had made the move successfully I realised that the folder I was moving to was not the one I wanted, and hit ‘cancel’ on the WinXP file moving dialog box. The movement was cancelled as I wanted. HOWEVER, while the files that had been moved completely were still present in the destination, to my horror, the folders that hadn’t been moved yet were gone! :sad:. It was as if the NSLU2’s SAMBA implementation considered the entire move successful, and deleted the source folders. :(

    Anyone else experienced this?

    I ran an NSLU2 scandisk on the ext3 partition afterward, but it claimed nothing was wrong. :cry:
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice