Re: ext3 filesystem and file name restrictions

[Tzafrir Cohen]

On Wed, Oct 15, 2008 at 09:30:26PM +0200, Michelle Konzack wrote:
> Am 2008-10-15 11:05:24, schrieb Adam Hardy:
> > Is there a basis for the file name restrictions on ext3, i.e. can I say, 
> > well ext3 is based on a standard, so I'm going to restrict the file names 
> > on macs, otherwise they won't be backed up?
> 
> There are none.  You can even have a backslash in the Filename

But you can't have a slash in a file name. It is a directory separator.

-- 
Tzafrir Cohen | [EMAIL PROTECTED] | VIM is
http://tzafrir.org.il || a Mutt's
[EMAIL PROTECTED] ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Michelle Konzack]

Am 2008-10-15 11:05:24, schrieb Adam Hardy:
> Is there a basis for the file name restrictions on ext3, i.e. can I say, 
> well ext3 is based on a standard, so I'm going to restrict the file names 
> on macs, otherwise they won't be backed up?

There are none.  You can even have a backslash in the Filename

Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: ext3 filesystem and file name restrictions

[Rob McBroom]

On 2008-Oct-15, at 6:05 AM, Adam Hardy wrote:

I created a samba share on one of my debian boxes with a ext3 file  
system and unfortunately I can't write files with certain file names  
from Mac OSX.


This disrupts the back-up process which takes about an hour every  
time to fail when I want to try it out again.


I would create a sparse bundle (formatted as HFS+) on the Samba share  
and back up to that. This would mean an extra mount/unmount to access  
the filesystem, but you may be able to automate those steps depending  
on what your back-up process is.


I don't think you can create the bundle on the Samba share because of  
some unsupported locking or somesuch, so create it on your Mac and  
copy it over. (I think you will see an error on the copy, too, but the  
sparse bundle should work anyway in my experience. Also note that size  
you give to the sparse bundle is just a maximum. It will actually be  
quite small until you add files, so don't worry about creating it  
locally and moving it.)


Feel free to e-mail me directly if you need help with any of this. (or  
Google it. There are quite a few good articles out there.)


--
Rob McBroom


Because it screws up the order in which people normally read text.

Original message:


Why is it bad to top-post your reply?





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Paul Johnson]

Adam Hardy wrote:
> After finding out all I could about Mac file systems and names, my
> conclusion is that macs are pretty special, especially their file
> systems.
Funny thing is, the colon is a restricted character in Mac filesystems,
too... the colon at least until OS X (and possibly still in the finder)
use : as a filename seperator...



signature.asc
Description: OpenPGP digital signature

RE: ext3 filesystem and file name restrictions

[Tammo Schuelke]

After reading the comments here:
http://www.macosxhints.com/article.php?story=20031114045400715
I think the behaviour has been changed in Mac OS X, but the userspace tools 
seem to handle it inconsistently.
Also see http://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words.


> -Original Message-
> From: Adam Hardy [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2008 12:37 PM
> To: debian-user@lists.debian.org
> Cc: List Debian User
> Subject: Re: ext3 filesystem and file name restrictions
> 
> Tammo Schuelke on 15/10/08 11:15, wrote:
> >> -Original Message- From: Adam Hardy
> >> [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2008
> >> 12:05 PM To: List Debian User Subject: ext3 filesystem and file name
> >> restrictions
> >>
> >> Hi,
> >>
> >> I created a samba share on one of my debian boxes with a ext3 file system
> >> and unfortunately I can't write files with certain file names from Mac OSX.
> >>
> >>
> >>
> >> This disrupts the back-up process which takes about an hour every time to
> >> fail when I want to try it out again.
> >>
> >> For instance, there is one file name like this:
> >>
> >> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
> >>
> >> which has a colon in it that I guess is the problem.
> >>
> >> After finding out all I could about Mac file systems and names, my
> >> conclusion is that macs are pretty special, especially their file systems.
> >>
> >> Is there a basis for the file name restrictions on ext3, i.e. can I say,
> >> well ext3 is based on a standard, so I'm going to restrict the file names
> >> on macs, otherwise they won't be backed up?
> >
> > Have you tried creating a file with a colon in its name by hand? I just
> > tested it, both ext3 and samba don't have a problem with it (only Windows
> > clients don't like it). With which error message does it fail?
> 
> 
> Blast! I thought I was being clever and because I didn't want to confuse the
> issue, I actually changed that file name above. Originally the dialog box 
> error
> message on the mac had a slash instead of a colon:
> 
> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786/ABPerson.abcdp
> 
> I thought, uh-huh, let's find it then - but when I searched for it, all I 
> found
> was the name with the colon, so I figured that must be the problem file and 
> that
> the error handling had somehow 'escaped' the colon into a slash.
> 
> So I can only assume that there was some sort of temporary file with the slash
> in it then, which disappeared.
> 
> Yet I do seem to have a file name with a colon in it, despite that link from
> XvsXP. Here's the output from find:
> 
> 
> Last login: Wed Oct 15 10:03:23 on console
> Welcome to Darwin!
> sylvie-computer:~ sylvie$ find . -name *ABPerson*
> ./Library/Application Support/AddressBook/.skIndex.ABPerson.lockN
> ./Library/Application Support/AddressBook/ABPerson.skIndexInverted
> ./Library/Application Support/Quicksilver/PlugIns/iChat
> Module.qsplugin/Contents/Resources/ABPerson-Fez.h
> ./Library/Caches/com.apple.AddressBook/MetaData/2AE2EAEE-57AC-46D8-B619-
> C2167D4C6786:ABPerson.abcdp
> ./Library/Caches/com.apple.AddressBook/MetaData/4B1A764D-C182-4200-88DB-
> 0686716AAB89:ABPerson.abcdp
> sylvie-computer:~ sylvie$
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[John Hasler]

Adam writes:
> Is there a basis for the file name restrictions on ext3, i.e. can I say,
> well ext3 is based on a standard, so I'm going to restrict the file names
> on macs, otherwise they won't be backed up?

You can use any printable character other than '/'.  ':; is entirely legal
and often used: try 'locate ::'.
-- 
John Hasler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Aneurin Price]

On Wed, Oct 15, 2008 at 11:25 AM, Jochen Schulz <[EMAIL PROTECTED]> wrote:
> Adam Hardy:
>>
>> For instance, there is one file name like this:
>>
>> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
>>
>> which has a colon in it that I guess is the problem.
>
> I am not sure either, but I'd bet on that, too. I guess this is not even
> a problem with neither MacOS X or ext3 -- it might be a restriction you
> get because you are using samba. On Windows the colon has a special
> meaning in path names (it's exclusively used for drive letters like c:)

This isn't entirely true; the reason it's restricted it that it's used to denote
Alternate Data Streams.

In fact, NTFS supports the same filenames as ext3 or
other Posix-compatible filesystems, but the Win32 API does not. This means it's
possible to create a file that cannot be read/changed/deleted from within
Windows, unless you're using SFU, which is unavailable on 64-bit Windows. Even
Cygwin can't help since it's layered on top of the Win32 subsystem. Yes, I speak
from bitter experience :-(.

> and I wouldn't be surprised if this is reflected in their filesharing
> protocol as well.
>
> J.

This doesn't seem right however - I distinctly recall spending several hours
trying to figure out why I couldn't copy some files from a Samba share in
Windows, and eventually realising that I'd copied them from a Linux system
without checking for things like restricted file names, and sure enough some of
them had colons.

If it's a Samba restriction, then it's not in the protocol - maybe there's an
option that can be set in the Samba server?

-Nye


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Adam Hardy]

Tammo Schuelke on 15/10/08 11:15, wrote:
-Original Message- From: Adam Hardy 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2008 
12:05 PM To: List Debian User Subject: ext3 filesystem and file name 
restrictions


Hi,

I created a samba share on one of my debian boxes with a ext3 file system 
and unfortunately I can't write files with certain file names from Mac OSX.




This disrupts the back-up process which takes about an hour every time to 
fail when I want to try it out again.


For instance, there is one file name like this:

2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp

which has a colon in it that I guess is the problem.

After finding out all I could about Mac file systems and names, my 
conclusion is that macs are pretty special, especially their file systems.


Is there a basis for the file name restrictions on ext3, i.e. can I say, 
well ext3 is based on a standard, so I'm going to restrict the file names 
on macs, otherwise they won't be backed up?


Have you tried creating a file with a colon in its name by hand? I just 
tested it, both ext3 and samba don't have a problem with it (only Windows

clients don't like it). With which error message does it fail?



Blast! I thought I was being clever and because I didn't want to confuse the 
issue, I actually changed that file name above. Originally the dialog box error 
message on the mac had a slash instead of a colon:


2AE2EAEE-57AC-46D8-B619-C2167D4C6786/ABPerson.abcdp

I thought, uh-huh, let's find it then - but when I searched for it, all I found 
was the name with the colon, so I figured that must be the problem file and that 
the error handling had somehow 'escaped' the colon into a slash.


So I can only assume that there was some sort of temporary file with the slash 
in it then, which disappeared.


Yet I do seem to have a file name with a colon in it, despite that link from 
XvsXP. Here's the output from find:



Last login: Wed Oct 15 10:03:23 on console
Welcome to Darwin!
sylvie-computer:~ sylvie$ find . -name *ABPerson*
./Library/Application Support/AddressBook/.skIndex.ABPerson.lockN
./Library/Application Support/AddressBook/ABPerson.skIndexInverted
./Library/Application Support/Quicksilver/PlugIns/iChat 
Module.qsplugin/Contents/Resources/ABPerson-Fez.h

./Library/Caches/com.apple.AddressBook/MetaData/2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
./Library/Caches/com.apple.AddressBook/MetaData/4B1A764D-C182-4200-88DB-0686716AAB89:ABPerson.abcdp
sylvie-computer:~ sylvie$


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Jochen Schulz]

Adam Hardy:
> 
> For instance, there is one file name like this:
> 
> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
> 
> which has a colon in it that I guess is the problem.

I am not sure either, but I'd bet on that, too. I guess this is not even
a problem with neither MacOS X or ext3 -- it might be a restriction you
get because you are using samba. On Windows the colon has a special
meaning in path names (it's exclusively used for drive letters like c:)
and I wouldn't be surprised if this is reflected in their filesharing
protocol as well.

J.
-- 
Quite often I wonder why I am not more famous and/or more wealthy.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

RE: ext3 filesystem and file name restrictions

[Tammo Schuelke]

Have you tried creating a file with a colon in its name by hand?
I just tested it, both ext3 and samba don't have a problem with it (only 
Windows clients don't like it).
With which error message does it fail?

Tammo

> -Original Message-
> From: Adam Hardy [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2008 12:05 PM
> To: List Debian User
> Subject: ext3 filesystem and file name restrictions
> 
> Hi,
> 
> I created a samba share on one of my debian boxes with a ext3 file system and
> unfortunately I can't write files with certain file names from Mac OSX.
> 
> This disrupts the back-up process which takes about an hour every time to fail
> when I want to try it out again.
> 
> For instance, there is one file name like this:
> 
> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
> 
> which has a colon in it that I guess is the problem.
> 
> After finding out all I could about Mac file systems and names, my conclusion 
> is
> that macs are pretty special, especially their file systems.
> 
> Is there a basis for the file name restrictions on ext3, i.e. can I say, well
> ext3 is based on a standard, so I'm going to restrict the file names on macs,
> otherwise they won't be backed up?
> 
> 
> Thanks
> Adam
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RE: ext3 filesystem and file name restrictions

[Tammo Schuelke]

PS: the file with a colon in its name comes from a Mac? From what I just read, 
the Mac OS FS (HFS+) doesn't support colons in filenames.

http://www.xvsxp.com/files/forbidden.php

Tammo

> -Original Message-
> From: Adam Hardy [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2008 12:05 PM
> To: List Debian User
> Subject: ext3 filesystem and file name restrictions
> 
> Hi,
> 
> I created a samba share on one of my debian boxes with a ext3 file system and
> unfortunately I can't write files with certain file names from Mac OSX.
> 
> This disrupts the back-up process which takes about an hour every time to fail
> when I want to try it out again.
> 
> For instance, there is one file name like this:
> 
> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
> 
> which has a colon in it that I guess is the problem.
> 
> After finding out all I could about Mac file systems and names, my conclusion 
> is
> that macs are pretty special, especially their file systems.
> 
> Is there a basis for the file name restrictions on ext3, i.e. can I say, well
> ext3 is based on a standard, so I'm going to restrict the file names on macs,
> otherwise they won't be backed up?
> 
> 
> Thanks
> Adam
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ext3 filesystem and file name restrictions

[Sjoerd Hardeman]

Adam Hardy wrote:

Hi,

I created a samba share on one of my debian boxes with a ext3 file 
system and unfortunately I can't write files with certain file names 
from Mac OSX.


This disrupts the back-up process which takes about an hour every time 
to fail when I want to try it out again.


For instance, there is one file name like this:

2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp

which has a colon in it that I guess is the problem.

I don't think so:
$ touch test:test
$ ls test:test
test:test

so colons are not a problem. I also don't see any other character that 
should pose a problem, so I guess you have some other difficultly.


After finding out all I could about Mac file systems and names, my 
conclusion is that macs are pretty special, especially their file systems.


Is there a basis for the file name restrictions on ext3, i.e. can I say, 
well ext3 is based on a standard, so I'm going to restrict the file 
names on macs, otherwise they won't be backed up?



Thanks
Adam







signature.asc
Description: OpenPGP digital signature

RE: ext3 filesystem and file name restrictions

[Tammo Schuelke]

Have you tried creating a file with a colon in its name by hand?
I just tested it, both ext3 and samba don't have a problem with it (only 
Windows clients don't like it).
With which error message does it fail?

Tammo

> -Original Message-
> From: Adam Hardy [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2008 12:05 PM
> To: List Debian User
> Subject: ext3 filesystem and file name restrictions
> 
> Hi,
> 
> I created a samba share on one of my debian boxes with a ext3 file system and
> unfortunately I can't write files with certain file names from Mac OSX.
> 
> This disrupts the back-up process which takes about an hour every time to fail
> when I want to try it out again.
> 
> For instance, there is one file name like this:
> 
> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp
> 
> which has a colon in it that I guess is the problem.
> 
> After finding out all I could about Mac file systems and names, my conclusion 
> is
> that macs are pretty special, especially their file systems.
> 
> Is there a basis for the file name restrictions on ext3, i.e. can I say, well
> ext3 is based on a standard, so I'm going to restrict the file names on macs,
> otherwise they won't be backed up?
> 
> 
> Thanks
> Adam
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ext3 filesystem and file name restrictions

[Adam Hardy]

Hi,

I created a samba share on one of my debian boxes with a ext3 file system and 
unfortunately I can't write files with certain file names from Mac OSX.


This disrupts the back-up process which takes about an hour every time to fail 
when I want to try it out again.


For instance, there is one file name like this:

2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp

which has a colon in it that I guess is the problem.

After finding out all I could about Mac file systems and names, my conclusion is 
that macs are pretty special, especially their file systems.


Is there a basis for the file name restrictions on ext3, i.e. can I say, well 
ext3 is based on a standard, so I'm going to restrict the file names on macs, 
otherwise they won't be backed up?



Thanks
Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]