Linux File Limitations?

[Guest]

Just wondering what kind of limitations Linux has compared to Windows. I keep getting an annoying error like this in Windows and I was just wondering if Linux has limitations like this or not. It's kind of an essential question. 

 

[2FA]

It doesn't.

[jj9987]

On Windows (NTFS file system), filename itself is limited to 255 characters, and the total path length is 32,767 characters. Linux, assuming you use ext4, filename is limited to 255 bytes, but total path length limit is not defined.

[Guest]

I'm not sure if OS X has limitations like this as well, would be good if I got response about it. 

[Guest]

3 hours ago, DeadEyePsycho said:

It doesn't.

I guess that might be why everyone uses it for server use

[Enderman]

6 minutes ago, DeadEyePsycho said:

It doesn't.

it does

http://serverfault.com/questions/9546/filename-length-limits-on-linux

[Guest]

3 hours ago, jj9987 said:

On Windows (NTFS file system), filename itself is limited to 255 characters, and the total path length is 32,767 characters. Linux, assuming you use ext4, filename is still limited to 255 characters, but total path length limit is not defined.

what is ext4, I plan on trying out ubuntu, not sure if that has it

 

I wonder if it would be possible to hit the same error in linux then, it doesn't sound like it though 

[vanished]

I think what you mean to ask is what limitations do typical Linux filesystems have, not the OS itself.  I can tell you that they're generally better in every way.  They are case sensitive, unlike NTFS, they can (usually, not always) have longer file names, and they support more and different characters in filenames that Windows/NTFS would not.

[jj9987]

3 minutes ago, IAmLamp said:

what is ext4, I plan on trying out ubuntu, not sure if that has it

 

I wonder if it would be possible to hit the same error in linux then, it doesn't sound like it though 

EXT4 is the file system, that is most often used on desktop Linux environments.

 

On OS X (HFS+ file system), the limit is also 255 chars per filename and no limit for path.

[Guest]

3 hours ago, Ryan_Vickers said:

I think what you mean to ask is what limitations do typical Linux filesystems have, not the OS itself.  I can tell you that they're generally better in every way.  They are case sensitive, unlike NTFS, they can (usually, not always) have longer file names, and they support more and different characters in filenames that Windows/NTFS would not.

That actually sounds very attractive, is that for all linux distros or just some? I'm thinking about ubuntu 

[vanished]

1 minute ago, IAmLamp said:

That actually sounds very attractive, is that for all linux distros or just some? I'm thinking about ubuntu 

Anything that supports one of the good filesystems, like Reiser4, which should be any of them, but you'd have to check if it's included by default.

[PianoPlayer88Key]

I think, at least my version of Windows 10 (and 7 before it) is limited to 255 chars for the entire length.   I get that complaint even when a single folder or file might only be 100 chars.  I could understand limits like that when drives were only like 10-20 MB and several thousand bucks each (back in the early 1980s or so), but now when you can get double-digit terabytes for only triple-digit bucks?  I just don't understand having such limits.

[vanished]

I should mention too, that there is a lot that goes into making a filesystem good or bad.  Support for odd filenames is only one small aspect, and probably shouldn't be your highest priority.  I would look also for performance, reliability, and support for advanced features, but you can't really go wrong in those areas with something like EXT4

[Guest]

3 hours ago, PianoPlayer88Key said:

I think, at least my version of Windows 10 (and 7 before it) is limited to 255 chars for the entire length.   I get that complaint even when a single folder or file might only be 100 chars.  I could understand limits like that when drives were only like 10-20 MB and several thousand bucks each (back in the early 1980s or so), but now when you can get double-digit terabytes for only triple-digit bucks?  I just don't understand having such limits.

Yeah hopefully they'll make the switch to something better, but in the mean time that's actually a pretty large bottleneck for the work I do and plan on doing, that and I want to get extremely well organized 

[vanished]

10 minutes ago, jj9987 said:

On Windows (NTFS file system), filename itself is limited to 255 characters, and the total path length is 32,767 characters. Linux, assuming you use ext4, filename is limited to 255 bytes, but total path length limit is not defined.

Really?  I thought that the whole path was actually limited to 255 as well... (on windows)

[Guest]

3 hours ago, Ryan_Vickers said:

I should mention too, that there is a lot that goes into making a filesystem good or bad.  Support for odd filenames is only one small aspect, and probably shouldn't be your highest priority.  I would look also for performance, reliability, and support for advanced features, but you can't really go wrong in those areas with something like EXT4

Does OS X has limitations like the ones shown here specifically for Windows? 

[Enderman]

6 minutes ago, PianoPlayer88Key said:

I think, at least my version of Windows 10 (and 7 before it) is limited to 255 chars for the entire length.   I get that complaint even when a single folder or file might only be 100 chars.  I could understand limits like that when drives were only like 10-20 MB and several thousand bucks each (back in the early 1980s or so), but now when you can get double-digit terabytes for only triple-digit bucks?  I just don't understand having such limits.

255 characters for the FILE NAME

its 32000 characters for the path

 

10 minutes ago, IAmLamp said:

what is ext4, I plan on trying out ubuntu, not sure if that has it

 

I wonder if it would be possible to hit the same error in linux then, it doesn't sound like it though 

linux is 255 bytes

which using UTF 8 will be 255 characters

unless you use some characters outside the standard 256 bit table, in which case it will be less, down to 127 characters

so if you use just regular english letters and characters, thats the exact same as windows

[vanished]

2 minutes ago, Enderman said:

255 characters for the FILE NAME

its 32000 characters for the path

 

13 minutes ago, jj9987 said:

On Windows (NTFS file system), filename itself is limited to 255 characters, and the total path length is 32,767 characters. Linux, assuming you use ext4, filename is limited to 255 bytes, but total path length limit is not defined.

Really?  That's odd, since I just made a folder called "1234567890" and nested it 32 levels deep and hit a path length limit before reaching the end

[Enderman]

2 minutes ago, Ryan_Vickers said:

 

Really?  That's odd, since I just made a folder called "1234567890" and nested it 16 levels deep and hit a path length limit before reaching the end

http://stackoverflow.com/questions/265769/maximum-filename-length-in-ntfs-windows-xp-and-windows-vista

ntfs is

windows is shorter though

[vanished]

4 minutes ago, IAmLamp said:

Does OS X has limitations like the ones shown here specifically for Windows? 

You'd have to look up the limitations on HFS+.  I believe it is generally pretty good, but it may limit paths as well

[vanished]

2 minutes ago, Enderman said:

http://stackoverflow.com/questions/265769/maximum-filename-length-in-ntfs-windows-xp-and-windows-vista

ntfs is

windows is shorter though

Sorry, what are you saying?  I'm trying to claim that the path length in Windows/NTFS is also limited to something around 255 characters, and I seem to have just proven it too.  Are we actually agreeing on this or not... I can't tell

[Enderman]

4 minutes ago, Ryan_Vickers said:

 

Really?  That's odd, since I just made a folder called "1234567890" and nested it 16 levels deep and hit a path length limit before reaching the end

oh and also with windows 10 you can remove the 260 byte path limit

http://mspoweruser.com/ntfs-260-character-windows-10/

[Guest]

idk why he keeps commenting on my threads, i have him ignored 

[vanished]

2 minutes ago, Enderman said:

oh and also with windows 10 you can remove the 260 byte path limit

http://mspoweruser.com/ntfs-260-character-windows-10/

Interesting.  I'll check that out actually, thanks

But by default, it does seem to have a 255 character path length limit.  Whether this is Windows or NTFS I'm not sure actually but it does happen on Windows 10 for me right now.

[vanished]

4 minutes ago, Enderman said:

oh and also with windows 10 you can remove the 260 byte path limit

http://mspoweruser.com/ntfs-260-character-windows-10/

So I just checked Group Policy and I don't seem to have the key they mention...