HarryPutnam

New Member
Joined
Dec 2, 2010
Messages
4
Setup: Windows 7 Home Premium (64bit)

I've been accessing the same couple of mapped drive shares, that reside on a linux host thru several versions of windows, XP, Vista and now Win7.

I continue to get a rather ridiculous error message that only happens on win7 (I no longer have a Vista OS handy to test, but XP does not exhibit this problem) and am not allowed to rename directory (I will show the error in a moment)

Here is how it might come about:

I navigate into a mapped drive (residing on a linux host). Right click in Windows explorer and select `New Folder'.

The folder is created but due to a slight fumble I let it get away before giving it a meaningful name.
So now Right click `new folder' and select "rename". But I'm not allowed to rename it.

I know from experience this is not going to abate so I create another new folder but this time get it named in 1 go, and now go to the recalcitrant `new folder' and delete it.

So, I'm allowed to create folders, and delete folders, but not allowed to rename them.

The goofy error is: `The new file is too large for the destination filesystem'

Well, of course one might think perhaps the directory is full on the host.... But no, there are 64 GB available there on that share going by the linux reading, and 60 GB even by the windows reading with right click `properties' on the share.

Googling the error I find this problem happens when the filesystem is Fat32 etc.
Examining the Mapped drive with Properties, It says that the fs is NTFS. Which is of course wrong since it is a linux filesystem. formatted as Reiserfs and shared with the linux tool `samba'.


Does any of this sound familiar to anyone... does anyong know what is to be done about it?
 


Solution
The issue you are facing with being unable to rename folders on a mapped drive from a Linux host in Windows 7, accompanied by the error message "The new file is too large for the destination filesystem," is indeed a peculiar one. The error message you are encountering typically indicates a filesystem mismatch or compatibility issue between the Windows system and the filesystem of the Linux host. Here are some steps and considerations to address this problem: 1. Filesystem Compatibility: - Ensure that the Linux filesystem (ReiserFS in this case) is fully supported by Samba for sharing with Windows systems. Sometimes, certain filesystem features might not be fully compatible or supported by the Windows OS. 2. Samba...
The issue you are facing with being unable to rename folders on a mapped drive from a Linux host in Windows 7, accompanied by the error message "The new file is too large for the destination filesystem," is indeed a peculiar one. The error message you are encountering typically indicates a filesystem mismatch or compatibility issue between the Windows system and the filesystem of the Linux host. Here are some steps and considerations to address this problem: 1. Filesystem Compatibility: - Ensure that the Linux filesystem (ReiserFS in this case) is fully supported by Samba for sharing with Windows systems. Sometimes, certain filesystem features might not be fully compatible or supported by the Windows OS. 2. Samba Configuration: - Check the Samba configuration on the Linux host to ensure that it is correctly configured to share the ReiserFS filesystem. Verify the settings in the /etc/samba/smb.conf file. 3. Unicode Compatibility: - Ensure that the Samba configuration includes proper Unicode support, especially if special characters are involved in folder or file names. 4. Windows Profile: - Sometimes, user profile issues can lead to strange errors. Try accessing the mapped drive from a different Windows 7 user account to see if the issue persists. 5. Network Permissions: - Verify the permissions set on the shared folders on the Linux host. Make sure that the Windows user has the necessary permissions to rename files and folders. 6. Error Troubleshooting: - Attempt to reproduce the error with different scenarios (using different filenames, locations, etc.) to see if the issue is consistent or specific to certain conditions. If these steps do not resolve the issue, a workaround could involve creating and renaming folders directly on the Linux host and then accessing them from Windows. This method might bypass any potential translation issues through Samba. Given the specifics of your setup and the error message received, ensuring proper configuration of Samba for ReiserFS compatibility and verifying permissions and filesystem settings should be the primary focus in troubleshooting this problem.
 


Solution
Back
Top