Seems to be a securty hotfix, witch leaves us with a very limited UDF file system driver in the vanilla kernel...
Check out http://lkml.org/lkml/2006/9/4/64
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Up until the forcible removal of >1GB file write support, we did not have problems writing large files (4 to 20 GB) onto an UDF-formatted medium in the following 'backup-like' use case:
1. A large file is deleted
2. A new file with the same or similar name is created
3. That new file is linearly written up to a size of 4 to 20 GB
(Writing 32kB blocks using "something closely resembling tar")
4. That new file is closed
Up to now, we could not determine any problems with this usage pattern. The kernel memory corruption reported in http://lkml.org/lkml/2006/9/4/64 did not bite us - yet.
Can anyone shed light on whether the above-mentioned usage pattern is "OK to use", or whether this
usage pattern is also prone to corruption and we're simply lucky so far?
Thank you very much!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Seems to be a securty hotfix, witch leaves us with a very limited UDF file system driver in the vanilla kernel...
Check out http://lkml.org/lkml/2006/9/4/64
Logged In: YES
user_id=694961
Originator: NO
Confirmed same problem using DVD-RAM on both SuSE 10.1 and 10.2 and Fedora Core 6.
Logged In: YES
user_id=768932
Originator: NO
Up until the forcible removal of >1GB file write support, we did not have problems writing large files (4 to 20 GB) onto an UDF-formatted medium in the following 'backup-like' use case:
1. A large file is deleted
2. A new file with the same or similar name is created
3. That new file is linearly written up to a size of 4 to 20 GB
(Writing 32kB blocks using "something closely resembling tar")
4. That new file is closed
Up to now, we could not determine any problems with this usage pattern. The kernel memory corruption reported in http://lkml.org/lkml/2006/9/4/64 did not bite us - yet.
Can anyone shed light on whether the above-mentioned usage pattern is "OK to use", or whether this
usage pattern is also prone to corruption and we're simply lucky so far?
Thank you very much!
Logged In: NO
Same problem here ... OpenSuSE 10.2.
Please fix this quick! I need bigger files ... :)
Logged In: NO
I just ran into this limit, too. 8( 2.6.16.19 worked fine.