Can and should UDF be used as a hard drive format?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







30















Several time recently I've seen UDF suggested as the solution to a cross platform format for a drive used on Linux, Mac OS X and Windows XP and above.



I've searched here and not found the same suggestion (most are suggesting ntfs-3g which seems to cost money and isn't preinstalled on a Mac).



So my question is: how is this done right, and has anyone done this? Have you then filled up the drive and deleted some files to make space finding that everything works like a real r/w format even though it seems to have been primarily a write once format?



Call me crazy but I'd really like it if the UDF system would also automount and be writable by the logged in user. What I've tried so far (udftools formatting as mentioned by kicsyromy) doesn't address this wish.










share|improve this question




















  • 1





    One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

    – Eliah Kagan
    Jul 11 '13 at 23:44













  • @EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

    – user29020
    Apr 18 '14 at 20:49











  • @user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

    – Eliah Kagan
    May 2 '14 at 18:36






  • 1





    @user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

    – dlamblin
    Jul 21 '14 at 20:23


















30















Several time recently I've seen UDF suggested as the solution to a cross platform format for a drive used on Linux, Mac OS X and Windows XP and above.



I've searched here and not found the same suggestion (most are suggesting ntfs-3g which seems to cost money and isn't preinstalled on a Mac).



So my question is: how is this done right, and has anyone done this? Have you then filled up the drive and deleted some files to make space finding that everything works like a real r/w format even though it seems to have been primarily a write once format?



Call me crazy but I'd really like it if the UDF system would also automount and be writable by the logged in user. What I've tried so far (udftools formatting as mentioned by kicsyromy) doesn't address this wish.










share|improve this question




















  • 1





    One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

    – Eliah Kagan
    Jul 11 '13 at 23:44













  • @EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

    – user29020
    Apr 18 '14 at 20:49











  • @user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

    – Eliah Kagan
    May 2 '14 at 18:36






  • 1





    @user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

    – dlamblin
    Jul 21 '14 at 20:23














30












30








30


10






Several time recently I've seen UDF suggested as the solution to a cross platform format for a drive used on Linux, Mac OS X and Windows XP and above.



I've searched here and not found the same suggestion (most are suggesting ntfs-3g which seems to cost money and isn't preinstalled on a Mac).



So my question is: how is this done right, and has anyone done this? Have you then filled up the drive and deleted some files to make space finding that everything works like a real r/w format even though it seems to have been primarily a write once format?



Call me crazy but I'd really like it if the UDF system would also automount and be writable by the logged in user. What I've tried so far (udftools formatting as mentioned by kicsyromy) doesn't address this wish.










share|improve this question
















Several time recently I've seen UDF suggested as the solution to a cross platform format for a drive used on Linux, Mac OS X and Windows XP and above.



I've searched here and not found the same suggestion (most are suggesting ntfs-3g which seems to cost money and isn't preinstalled on a Mac).



So my question is: how is this done right, and has anyone done this? Have you then filled up the drive and deleted some files to make space finding that everything works like a real r/w format even though it seems to have been primarily a write once format?



Call me crazy but I'd really like it if the UDF system would also automount and be writable by the logged in user. What I've tried so far (udftools formatting as mentioned by kicsyromy) doesn't address this wish.







filesystem external-hdd udf






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 1 '11 at 19:35







dlamblin

















asked Feb 24 '11 at 18:58









dlamblindlamblin

3922615




3922615








  • 1





    One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

    – Eliah Kagan
    Jul 11 '13 at 23:44













  • @EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

    – user29020
    Apr 18 '14 at 20:49











  • @user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

    – Eliah Kagan
    May 2 '14 at 18:36






  • 1





    @user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

    – dlamblin
    Jul 21 '14 at 20:23














  • 1





    One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

    – Eliah Kagan
    Jul 11 '13 at 23:44













  • @EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

    – user29020
    Apr 18 '14 at 20:49











  • @user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

    – Eliah Kagan
    May 2 '14 at 18:36






  • 1





    @user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

    – dlamblin
    Jul 21 '14 at 20:23








1




1





One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

– Eliah Kagan
Jul 11 '13 at 23:44







One clarification: ntfs-3g is free. Its source code is gratis (i.e., available at no cost). It is also free as in freedom. ntfs-3g is the NTFS driver in Ubuntu! It's slightly technical to manually build/install it on OS X, and Tuxera (its developer) offers a proprietary payware version that is essentially the free ntfs-3g driver built and packaged for easy installation and use on OS X. Without an add-on driver, OS X will only read (not write) NTFS volumes, so you're right to consider another filesystem.

– Eliah Kagan
Jul 11 '13 at 23:44















@EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

– user29020
Apr 18 '14 at 20:49





@EliahKagan So if ntfs-3g is "free", then why hasn't Apple included it to allow r/w support for NTFS?

– user29020
Apr 18 '14 at 20:49













@user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

– Eliah Kagan
May 2 '14 at 18:36





@user29020 I don't know while Apple chooses not to include it, but you can verify it's free by downloading the source code (currently this file), extracting it, and seeing that the COPYING file is the GNU GPL. Maybe Apple didn't want to do the work integrate it so it be used seamlessly from the Finder. See also tuxera.com/products/tuxera-ntfs-for-mac and sourceforge.net/projects/catacombae.

– Eliah Kagan
May 2 '14 at 18:36




1




1





@user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

– dlamblin
Jul 21 '14 at 20:23





@user29020 Support costs (what if it's a bit buggy)? Legal restrictions? Free under GNU GPL License means that it can only be added to existing source / binaries which are in turn also available under the GPL. (LGPL would allow it to be used as a library by other non-GPL code). Given that apple's code is largely proprietary and otherwise under the APSL which is not a GPL compatible license, that is a restriction they must abide by. gnu.org/philosophy/apsl.html

– dlamblin
Jul 21 '14 at 20:23










3 Answers
3






active

oldest

votes


















13














No.



We're in 2015 at the time of this reply. I am using OSX Yosemite, Ubuntu 14.10, and the Windows 10 technical preview for enterprises on a Mactel machine (Macmini 7,1).



I tried both UDF and exFat. I use Ubuntu for development and do need Unix-style permissions.



All former guides do not apply anymore: UDF drivers have evolved and all operating systems will accept a UDF partition, with more problems and instabilities than I can name.




  • UDF drive formatted on Mac OS: can't be mounted on Windows 10.

  • UDF drive formatted on Linux: can't be mounted on Windows 10.

  • UDF drive formatted on Windows 10: mounts read/write on Linux, read-only on OSX.


However, Windows doesn't allow you to specify a block size when formatting a UDF volume, and as a result, your logical block size might differ from the physical block size for the partition.



I am unclear whether this has to do with the difficulties I had mounting it read/write on OSX, but after deleting a certain number of files using Linux, I was never able to mount the drive again on OSX.



The system goes into kernel panic and crashes disgracefully.



This, and a variety of answers on the subject, indicate inconsistent support for this format at this point.



It would seem there are ways I can use a NTFS volume to achieve a balance between the features of a modern file system, Unix-style permissions - I might be able to set them - and read/write mount on all operating systems.






share|improve this answer





















  • 1





    OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

    – Mauro Colella
    Mar 19 '15 at 5:05






  • 1





    Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

    – Mauro Colella
    Apr 2 '15 at 6:37








  • 1





    @Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

    – JDługosz
    Apr 3 '15 at 10:25






  • 1





    The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

    – DrYak
    Mar 23 '16 at 16:26






  • 2





    There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

    – velop
    Jun 14 '16 at 9:20



















14














Someone did some research into how to format a flash drive with udf so it can be used on as many operating systems as possible. Here are his findings (used to be there, now offline):




  • Windows 7 have full support up to UDF v2.6, but the UDF block size must match the block size of the underlying device (which for USB-sticks and most disks is 512 bytes; "advanced format" disks are 4096 bytes). Apparently the disk must be partitioned.


  • Linux 2.6.30 and up supports UDF fully at least up to version 2.5.


  • Mac OS X 10.5 supports UDF fully up to UDF 2.01, but only when used on a full disk, so not partitioned.



As explained above, for USB harddisks, Windows requires the disk to be partitioned. On the other side, UDF only works in OS X when it is used on a full disk (unpartitioned). Rather surprisingly, there is a solution which works for both: having the disk partitioned and unpartitioned at the same time.



DOS partition tables are stored in bytes 446-510 of the master boot record. This master boot record is stored in the first sector on disk, sector 0. Typically, the first partition specified will start some kilobytes further. However, it seems possible to construct a partition table whose first partition starts at sector 0, so the result is a partition which contains the partition table itself. Partition editor programs seem to refuse to create such a table, but at least recent Linux and Windows kernels donu2019t seem to bother.



The nice thing is that UDF does not (I suppose deliberately) use the first few kilobytes of the partition or disk it is placed on, so this place can really be used to store a legacy partition table, referring to a partition that spans the whole disk. Some testing shows that this really works on Linux, Windows and Mac OS X:




  • Mounts automatically read-write in Linux 2.6.30+, Mac OS X 10.5+, Windows Vista+

  • Can be used read-only in Windows XP, and be used after a command line mount in Linux 2.6.0+

  • Supports large files, UNIX permissions, Unicode filenames, symlinks, hardlinks, etc.


Script to format the disk properly: Perl script or Bash script






share|improve this answer





















  • 3





    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

    – Eliah Kagan
    Jul 11 '13 at 23:45













  • @EliahKagan Thanks for the suggestion. I'll do that next time.

    – Dan Benamy
    Jul 13 '13 at 4:48











  • I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

    – Dan Benamy
    Jul 13 '13 at 4:49






  • 1





    Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

    – DrYak
    Mar 23 '16 at 16:29






  • 1





    While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

    – Timo
    Mar 30 '16 at 17:29



















12














I just tested this out in a VM. It seems that you need to (re)create your partition in Windows assign it a drive letter but don't format it to any filesystem. After that boot into Ubuntu and just follow the directions and it should work for read/write.



Remember to backup all your data!



First off install UDF tools:



sudo apt-get install udftools


Replace the first block with nothing on the partition you wish to format to UDF^:



sudo dd if=/dev/zero of=/dev/sdxN bs=512 count=1


And finally format to UDF^:



sudo mkudffs --media-type=hd --blocksize=512 /dev/sdxN


^where by:




  • x is a placeholder for the letter curently assigned to your hardisk


  • N is a placeholder for the partition number



Best of luck and let me know if it worked out for you.






share|improve this answer


























  • Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

    – dlamblin
    Feb 25 '11 at 0:17











  • This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

    – Nemo
    Sep 3 '12 at 0:47











  • The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

    – DanMan
    Nov 3 '12 at 23:57











  • @DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

    – dlamblin
    Jul 10 '13 at 16:10













  • @kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

    – Tim Banchi
    Jun 27 '14 at 10:51












protected by Community Mar 19 '15 at 5:06



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?














3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









13














No.



We're in 2015 at the time of this reply. I am using OSX Yosemite, Ubuntu 14.10, and the Windows 10 technical preview for enterprises on a Mactel machine (Macmini 7,1).



I tried both UDF and exFat. I use Ubuntu for development and do need Unix-style permissions.



All former guides do not apply anymore: UDF drivers have evolved and all operating systems will accept a UDF partition, with more problems and instabilities than I can name.




  • UDF drive formatted on Mac OS: can't be mounted on Windows 10.

  • UDF drive formatted on Linux: can't be mounted on Windows 10.

  • UDF drive formatted on Windows 10: mounts read/write on Linux, read-only on OSX.


However, Windows doesn't allow you to specify a block size when formatting a UDF volume, and as a result, your logical block size might differ from the physical block size for the partition.



I am unclear whether this has to do with the difficulties I had mounting it read/write on OSX, but after deleting a certain number of files using Linux, I was never able to mount the drive again on OSX.



The system goes into kernel panic and crashes disgracefully.



This, and a variety of answers on the subject, indicate inconsistent support for this format at this point.



It would seem there are ways I can use a NTFS volume to achieve a balance between the features of a modern file system, Unix-style permissions - I might be able to set them - and read/write mount on all operating systems.






share|improve this answer





















  • 1





    OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

    – Mauro Colella
    Mar 19 '15 at 5:05






  • 1





    Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

    – Mauro Colella
    Apr 2 '15 at 6:37








  • 1





    @Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

    – JDługosz
    Apr 3 '15 at 10:25






  • 1





    The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

    – DrYak
    Mar 23 '16 at 16:26






  • 2





    There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

    – velop
    Jun 14 '16 at 9:20
















13














No.



We're in 2015 at the time of this reply. I am using OSX Yosemite, Ubuntu 14.10, and the Windows 10 technical preview for enterprises on a Mactel machine (Macmini 7,1).



I tried both UDF and exFat. I use Ubuntu for development and do need Unix-style permissions.



All former guides do not apply anymore: UDF drivers have evolved and all operating systems will accept a UDF partition, with more problems and instabilities than I can name.




  • UDF drive formatted on Mac OS: can't be mounted on Windows 10.

  • UDF drive formatted on Linux: can't be mounted on Windows 10.

  • UDF drive formatted on Windows 10: mounts read/write on Linux, read-only on OSX.


However, Windows doesn't allow you to specify a block size when formatting a UDF volume, and as a result, your logical block size might differ from the physical block size for the partition.



I am unclear whether this has to do with the difficulties I had mounting it read/write on OSX, but after deleting a certain number of files using Linux, I was never able to mount the drive again on OSX.



The system goes into kernel panic and crashes disgracefully.



This, and a variety of answers on the subject, indicate inconsistent support for this format at this point.



It would seem there are ways I can use a NTFS volume to achieve a balance between the features of a modern file system, Unix-style permissions - I might be able to set them - and read/write mount on all operating systems.






share|improve this answer





















  • 1





    OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

    – Mauro Colella
    Mar 19 '15 at 5:05






  • 1





    Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

    – Mauro Colella
    Apr 2 '15 at 6:37








  • 1





    @Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

    – JDługosz
    Apr 3 '15 at 10:25






  • 1





    The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

    – DrYak
    Mar 23 '16 at 16:26






  • 2





    There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

    – velop
    Jun 14 '16 at 9:20














13












13








13







No.



We're in 2015 at the time of this reply. I am using OSX Yosemite, Ubuntu 14.10, and the Windows 10 technical preview for enterprises on a Mactel machine (Macmini 7,1).



I tried both UDF and exFat. I use Ubuntu for development and do need Unix-style permissions.



All former guides do not apply anymore: UDF drivers have evolved and all operating systems will accept a UDF partition, with more problems and instabilities than I can name.




  • UDF drive formatted on Mac OS: can't be mounted on Windows 10.

  • UDF drive formatted on Linux: can't be mounted on Windows 10.

  • UDF drive formatted on Windows 10: mounts read/write on Linux, read-only on OSX.


However, Windows doesn't allow you to specify a block size when formatting a UDF volume, and as a result, your logical block size might differ from the physical block size for the partition.



I am unclear whether this has to do with the difficulties I had mounting it read/write on OSX, but after deleting a certain number of files using Linux, I was never able to mount the drive again on OSX.



The system goes into kernel panic and crashes disgracefully.



This, and a variety of answers on the subject, indicate inconsistent support for this format at this point.



It would seem there are ways I can use a NTFS volume to achieve a balance between the features of a modern file system, Unix-style permissions - I might be able to set them - and read/write mount on all operating systems.






share|improve this answer















No.



We're in 2015 at the time of this reply. I am using OSX Yosemite, Ubuntu 14.10, and the Windows 10 technical preview for enterprises on a Mactel machine (Macmini 7,1).



I tried both UDF and exFat. I use Ubuntu for development and do need Unix-style permissions.



All former guides do not apply anymore: UDF drivers have evolved and all operating systems will accept a UDF partition, with more problems and instabilities than I can name.




  • UDF drive formatted on Mac OS: can't be mounted on Windows 10.

  • UDF drive formatted on Linux: can't be mounted on Windows 10.

  • UDF drive formatted on Windows 10: mounts read/write on Linux, read-only on OSX.


However, Windows doesn't allow you to specify a block size when formatting a UDF volume, and as a result, your logical block size might differ from the physical block size for the partition.



I am unclear whether this has to do with the difficulties I had mounting it read/write on OSX, but after deleting a certain number of files using Linux, I was never able to mount the drive again on OSX.



The system goes into kernel panic and crashes disgracefully.



This, and a variety of answers on the subject, indicate inconsistent support for this format at this point.



It would seem there are ways I can use a NTFS volume to achieve a balance between the features of a modern file system, Unix-style permissions - I might be able to set them - and read/write mount on all operating systems.







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 24 '15 at 2:53

























answered Feb 2 '15 at 0:20









Mauro ColellaMauro Colella

35635




35635








  • 1





    OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

    – Mauro Colella
    Mar 19 '15 at 5:05






  • 1





    Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

    – Mauro Colella
    Apr 2 '15 at 6:37








  • 1





    @Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

    – JDługosz
    Apr 3 '15 at 10:25






  • 1





    The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

    – DrYak
    Mar 23 '16 at 16:26






  • 2





    There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

    – velop
    Jun 14 '16 at 9:20














  • 1





    OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

    – Mauro Colella
    Mar 19 '15 at 5:05






  • 1





    Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

    – Mauro Colella
    Apr 2 '15 at 6:37








  • 1





    @Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

    – JDługosz
    Apr 3 '15 at 10:25






  • 1





    The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

    – DrYak
    Mar 23 '16 at 16:26






  • 2





    There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

    – velop
    Jun 14 '16 at 9:20








1




1





OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

– Mauro Colella
Mar 19 '15 at 5:05





OSX is based on BSD. So yes, it is OSX Yosemite (10.10.2) which experiences a kernel panic. I ended up using NTFS, and NTFS 3d for OSX.

– Mauro Colella
Mar 19 '15 at 5:05




1




1





Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

– Mauro Colella
Apr 2 '15 at 6:37







Apparently not. See: manpages.ubuntu.com/manpages/lucid/man1/mkudffs.1.html and tanguy.ortolo.eu/blog/article93/usb-udf

– Mauro Colella
Apr 2 '15 at 6:37






1




1





@Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

– JDługosz
Apr 3 '15 at 10:25





@Argo the second reference states, "The -b 512 is to force a file system block size equal to the USB stick's physical block size, as required by the UDF specification. Adapt it if you have the luck of having a USB stick with an more appropriate block size." So it does let you specify the block size but it must be specified as being the required value.

– JDługosz
Apr 3 '15 at 10:25




1




1





The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

– DrYak
Mar 23 '16 at 16:26





The Windows 10 not mounted by OS X / OS X not mounted is due to difference in how each OS handle partition tables. Windows 10 : Needs one. Mac OS X: Needs UDF to be on the bare drive, as a whole drive partition.

– DrYak
Mar 23 '16 at 16:26




2




2





There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

– velop
Jun 14 '16 at 9:20





There is a formating tool which takes care of the incosistencies: github.com/JElchison/format-udf

– velop
Jun 14 '16 at 9:20













14














Someone did some research into how to format a flash drive with udf so it can be used on as many operating systems as possible. Here are his findings (used to be there, now offline):




  • Windows 7 have full support up to UDF v2.6, but the UDF block size must match the block size of the underlying device (which for USB-sticks and most disks is 512 bytes; "advanced format" disks are 4096 bytes). Apparently the disk must be partitioned.


  • Linux 2.6.30 and up supports UDF fully at least up to version 2.5.


  • Mac OS X 10.5 supports UDF fully up to UDF 2.01, but only when used on a full disk, so not partitioned.



As explained above, for USB harddisks, Windows requires the disk to be partitioned. On the other side, UDF only works in OS X when it is used on a full disk (unpartitioned). Rather surprisingly, there is a solution which works for both: having the disk partitioned and unpartitioned at the same time.



DOS partition tables are stored in bytes 446-510 of the master boot record. This master boot record is stored in the first sector on disk, sector 0. Typically, the first partition specified will start some kilobytes further. However, it seems possible to construct a partition table whose first partition starts at sector 0, so the result is a partition which contains the partition table itself. Partition editor programs seem to refuse to create such a table, but at least recent Linux and Windows kernels donu2019t seem to bother.



The nice thing is that UDF does not (I suppose deliberately) use the first few kilobytes of the partition or disk it is placed on, so this place can really be used to store a legacy partition table, referring to a partition that spans the whole disk. Some testing shows that this really works on Linux, Windows and Mac OS X:




  • Mounts automatically read-write in Linux 2.6.30+, Mac OS X 10.5+, Windows Vista+

  • Can be used read-only in Windows XP, and be used after a command line mount in Linux 2.6.0+

  • Supports large files, UNIX permissions, Unicode filenames, symlinks, hardlinks, etc.


Script to format the disk properly: Perl script or Bash script






share|improve this answer





















  • 3





    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

    – Eliah Kagan
    Jul 11 '13 at 23:45













  • @EliahKagan Thanks for the suggestion. I'll do that next time.

    – Dan Benamy
    Jul 13 '13 at 4:48











  • I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

    – Dan Benamy
    Jul 13 '13 at 4:49






  • 1





    Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

    – DrYak
    Mar 23 '16 at 16:29






  • 1





    While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

    – Timo
    Mar 30 '16 at 17:29
















14














Someone did some research into how to format a flash drive with udf so it can be used on as many operating systems as possible. Here are his findings (used to be there, now offline):




  • Windows 7 have full support up to UDF v2.6, but the UDF block size must match the block size of the underlying device (which for USB-sticks and most disks is 512 bytes; "advanced format" disks are 4096 bytes). Apparently the disk must be partitioned.


  • Linux 2.6.30 and up supports UDF fully at least up to version 2.5.


  • Mac OS X 10.5 supports UDF fully up to UDF 2.01, but only when used on a full disk, so not partitioned.



As explained above, for USB harddisks, Windows requires the disk to be partitioned. On the other side, UDF only works in OS X when it is used on a full disk (unpartitioned). Rather surprisingly, there is a solution which works for both: having the disk partitioned and unpartitioned at the same time.



DOS partition tables are stored in bytes 446-510 of the master boot record. This master boot record is stored in the first sector on disk, sector 0. Typically, the first partition specified will start some kilobytes further. However, it seems possible to construct a partition table whose first partition starts at sector 0, so the result is a partition which contains the partition table itself. Partition editor programs seem to refuse to create such a table, but at least recent Linux and Windows kernels donu2019t seem to bother.



The nice thing is that UDF does not (I suppose deliberately) use the first few kilobytes of the partition or disk it is placed on, so this place can really be used to store a legacy partition table, referring to a partition that spans the whole disk. Some testing shows that this really works on Linux, Windows and Mac OS X:




  • Mounts automatically read-write in Linux 2.6.30+, Mac OS X 10.5+, Windows Vista+

  • Can be used read-only in Windows XP, and be used after a command line mount in Linux 2.6.0+

  • Supports large files, UNIX permissions, Unicode filenames, symlinks, hardlinks, etc.


Script to format the disk properly: Perl script or Bash script






share|improve this answer





















  • 3





    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

    – Eliah Kagan
    Jul 11 '13 at 23:45













  • @EliahKagan Thanks for the suggestion. I'll do that next time.

    – Dan Benamy
    Jul 13 '13 at 4:48











  • I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

    – Dan Benamy
    Jul 13 '13 at 4:49






  • 1





    Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

    – DrYak
    Mar 23 '16 at 16:29






  • 1





    While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

    – Timo
    Mar 30 '16 at 17:29














14












14








14







Someone did some research into how to format a flash drive with udf so it can be used on as many operating systems as possible. Here are his findings (used to be there, now offline):




  • Windows 7 have full support up to UDF v2.6, but the UDF block size must match the block size of the underlying device (which for USB-sticks and most disks is 512 bytes; "advanced format" disks are 4096 bytes). Apparently the disk must be partitioned.


  • Linux 2.6.30 and up supports UDF fully at least up to version 2.5.


  • Mac OS X 10.5 supports UDF fully up to UDF 2.01, but only when used on a full disk, so not partitioned.



As explained above, for USB harddisks, Windows requires the disk to be partitioned. On the other side, UDF only works in OS X when it is used on a full disk (unpartitioned). Rather surprisingly, there is a solution which works for both: having the disk partitioned and unpartitioned at the same time.



DOS partition tables are stored in bytes 446-510 of the master boot record. This master boot record is stored in the first sector on disk, sector 0. Typically, the first partition specified will start some kilobytes further. However, it seems possible to construct a partition table whose first partition starts at sector 0, so the result is a partition which contains the partition table itself. Partition editor programs seem to refuse to create such a table, but at least recent Linux and Windows kernels donu2019t seem to bother.



The nice thing is that UDF does not (I suppose deliberately) use the first few kilobytes of the partition or disk it is placed on, so this place can really be used to store a legacy partition table, referring to a partition that spans the whole disk. Some testing shows that this really works on Linux, Windows and Mac OS X:




  • Mounts automatically read-write in Linux 2.6.30+, Mac OS X 10.5+, Windows Vista+

  • Can be used read-only in Windows XP, and be used after a command line mount in Linux 2.6.0+

  • Supports large files, UNIX permissions, Unicode filenames, symlinks, hardlinks, etc.


Script to format the disk properly: Perl script or Bash script






share|improve this answer















Someone did some research into how to format a flash drive with udf so it can be used on as many operating systems as possible. Here are his findings (used to be there, now offline):




  • Windows 7 have full support up to UDF v2.6, but the UDF block size must match the block size of the underlying device (which for USB-sticks and most disks is 512 bytes; "advanced format" disks are 4096 bytes). Apparently the disk must be partitioned.


  • Linux 2.6.30 and up supports UDF fully at least up to version 2.5.


  • Mac OS X 10.5 supports UDF fully up to UDF 2.01, but only when used on a full disk, so not partitioned.



As explained above, for USB harddisks, Windows requires the disk to be partitioned. On the other side, UDF only works in OS X when it is used on a full disk (unpartitioned). Rather surprisingly, there is a solution which works for both: having the disk partitioned and unpartitioned at the same time.



DOS partition tables are stored in bytes 446-510 of the master boot record. This master boot record is stored in the first sector on disk, sector 0. Typically, the first partition specified will start some kilobytes further. However, it seems possible to construct a partition table whose first partition starts at sector 0, so the result is a partition which contains the partition table itself. Partition editor programs seem to refuse to create such a table, but at least recent Linux and Windows kernels donu2019t seem to bother.



The nice thing is that UDF does not (I suppose deliberately) use the first few kilobytes of the partition or disk it is placed on, so this place can really be used to store a legacy partition table, referring to a partition that spans the whole disk. Some testing shows that this really works on Linux, Windows and Mac OS X:




  • Mounts automatically read-write in Linux 2.6.30+, Mac OS X 10.5+, Windows Vista+

  • Can be used read-only in Windows XP, and be used after a command line mount in Linux 2.6.0+

  • Supports large files, UNIX permissions, Unicode filenames, symlinks, hardlinks, etc.


Script to format the disk properly: Perl script or Bash script







share|improve this answer














share|improve this answer



share|improve this answer








edited 10 hours ago









clearkimura

4,30821958




4,30821958










answered May 13 '13 at 14:15









Dan BenamyDan Benamy

36036




36036








  • 3





    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

    – Eliah Kagan
    Jul 11 '13 at 23:45













  • @EliahKagan Thanks for the suggestion. I'll do that next time.

    – Dan Benamy
    Jul 13 '13 at 4:48











  • I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

    – Dan Benamy
    Jul 13 '13 at 4:49






  • 1





    Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

    – DrYak
    Mar 23 '16 at 16:29






  • 1





    While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

    – Timo
    Mar 30 '16 at 17:29














  • 3





    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

    – Eliah Kagan
    Jul 11 '13 at 23:45













  • @EliahKagan Thanks for the suggestion. I'll do that next time.

    – Dan Benamy
    Jul 13 '13 at 4:48











  • I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

    – Dan Benamy
    Jul 13 '13 at 4:49






  • 1





    Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

    – DrYak
    Mar 23 '16 at 16:29






  • 1





    While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

    – Timo
    Mar 30 '16 at 17:29








3




3





Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

– Eliah Kagan
Jul 11 '13 at 23:45







Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the links for reference.

– Eliah Kagan
Jul 11 '13 at 23:45















@EliahKagan Thanks for the suggestion. I'll do that next time.

– Dan Benamy
Jul 13 '13 at 4:48





@EliahKagan Thanks for the suggestion. I'll do that next time.

– Dan Benamy
Jul 13 '13 at 4:48













I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

– Dan Benamy
Jul 13 '13 at 4:49





I tried some variations on the instructions I linked to above and couldn't get a disk that worked on different versions of OS X.

– Dan Benamy
Jul 13 '13 at 4:49




1




1





Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

– DrYak
Mar 23 '16 at 16:29





Also, as pointed on ameenross git hub, there's a newer better tool: github.com/JElchison/format-udf

– DrYak
Mar 23 '16 at 16:29




1




1





While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

– Timo
Mar 30 '16 at 17:29





While this may be the best option (if you truly want to go UDF), my experience is that on a mac a disk created this way theoretically seemed to work, especially if you only used it with console, but then if you moved/created/deleted files using GUI the disk often got "jammed", files were put in recycle bin but the bin could not be emptied. So, I'd still personally recommend against UDF from my own experience though ofc YMMV.

– Timo
Mar 30 '16 at 17:29











12














I just tested this out in a VM. It seems that you need to (re)create your partition in Windows assign it a drive letter but don't format it to any filesystem. After that boot into Ubuntu and just follow the directions and it should work for read/write.



Remember to backup all your data!



First off install UDF tools:



sudo apt-get install udftools


Replace the first block with nothing on the partition you wish to format to UDF^:



sudo dd if=/dev/zero of=/dev/sdxN bs=512 count=1


And finally format to UDF^:



sudo mkudffs --media-type=hd --blocksize=512 /dev/sdxN


^where by:




  • x is a placeholder for the letter curently assigned to your hardisk


  • N is a placeholder for the partition number



Best of luck and let me know if it worked out for you.






share|improve this answer


























  • Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

    – dlamblin
    Feb 25 '11 at 0:17











  • This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

    – Nemo
    Sep 3 '12 at 0:47











  • The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

    – DanMan
    Nov 3 '12 at 23:57











  • @DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

    – dlamblin
    Jul 10 '13 at 16:10













  • @kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

    – Tim Banchi
    Jun 27 '14 at 10:51


















12














I just tested this out in a VM. It seems that you need to (re)create your partition in Windows assign it a drive letter but don't format it to any filesystem. After that boot into Ubuntu and just follow the directions and it should work for read/write.



Remember to backup all your data!



First off install UDF tools:



sudo apt-get install udftools


Replace the first block with nothing on the partition you wish to format to UDF^:



sudo dd if=/dev/zero of=/dev/sdxN bs=512 count=1


And finally format to UDF^:



sudo mkudffs --media-type=hd --blocksize=512 /dev/sdxN


^where by:




  • x is a placeholder for the letter curently assigned to your hardisk


  • N is a placeholder for the partition number



Best of luck and let me know if it worked out for you.






share|improve this answer


























  • Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

    – dlamblin
    Feb 25 '11 at 0:17











  • This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

    – Nemo
    Sep 3 '12 at 0:47











  • The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

    – DanMan
    Nov 3 '12 at 23:57











  • @DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

    – dlamblin
    Jul 10 '13 at 16:10













  • @kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

    – Tim Banchi
    Jun 27 '14 at 10:51
















12












12








12







I just tested this out in a VM. It seems that you need to (re)create your partition in Windows assign it a drive letter but don't format it to any filesystem. After that boot into Ubuntu and just follow the directions and it should work for read/write.



Remember to backup all your data!



First off install UDF tools:



sudo apt-get install udftools


Replace the first block with nothing on the partition you wish to format to UDF^:



sudo dd if=/dev/zero of=/dev/sdxN bs=512 count=1


And finally format to UDF^:



sudo mkudffs --media-type=hd --blocksize=512 /dev/sdxN


^where by:




  • x is a placeholder for the letter curently assigned to your hardisk


  • N is a placeholder for the partition number



Best of luck and let me know if it worked out for you.






share|improve this answer















I just tested this out in a VM. It seems that you need to (re)create your partition in Windows assign it a drive letter but don't format it to any filesystem. After that boot into Ubuntu and just follow the directions and it should work for read/write.



Remember to backup all your data!



First off install UDF tools:



sudo apt-get install udftools


Replace the first block with nothing on the partition you wish to format to UDF^:



sudo dd if=/dev/zero of=/dev/sdxN bs=512 count=1


And finally format to UDF^:



sudo mkudffs --media-type=hd --blocksize=512 /dev/sdxN


^where by:




  • x is a placeholder for the letter curently assigned to your hardisk


  • N is a placeholder for the partition number



Best of luck and let me know if it worked out for you.







share|improve this answer














share|improve this answer



share|improve this answer








edited 8 hours ago









clearkimura

4,30821958




4,30821958










answered Feb 24 '11 at 20:31









kicsyromykicsyromy

485418




485418













  • Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

    – dlamblin
    Feb 25 '11 at 0:17











  • This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

    – Nemo
    Sep 3 '12 at 0:47











  • The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

    – DanMan
    Nov 3 '12 at 23:57











  • @DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

    – dlamblin
    Jul 10 '13 at 16:10













  • @kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

    – Tim Banchi
    Jun 27 '14 at 10:51





















  • Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

    – dlamblin
    Feb 25 '11 at 0:17











  • This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

    – Nemo
    Sep 3 '12 at 0:47











  • The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

    – DanMan
    Nov 3 '12 at 23:57











  • @DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

    – dlamblin
    Jul 10 '13 at 16:10













  • @kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

    – Tim Banchi
    Jun 27 '14 at 10:51



















Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

– dlamblin
Feb 25 '11 at 0:17





Thanks this answers the how; I would still be interested in finding out if it works well enough with the above scenario.

– dlamblin
Feb 25 '11 at 0:17













This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

– Nemo
Sep 3 '12 at 0:47





This worked perfectly for me. The only issue is that I have to manually mount the partition in Windows using Disk Manager. Other than that, I can confirm that it works with multiple partitions on the hard-disk as well (I'm using 1udf+2ext4)

– Nemo
Sep 3 '12 at 0:47













The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

– DanMan
Nov 3 '12 at 23:57





The key here seems to be to actually create a partition and then create a UDF file system in there. If you don't create any partition, it'll work in Linux, but it won't in Windows (7). That's my experience.

– DanMan
Nov 3 '12 at 23:57













@DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

– dlamblin
Jul 10 '13 at 16:10







@DanMan Dan seems to have found someone who solved that issue and provides a script for formatting a whole disk with UDF for Linux, Mac and Windows 7, as well as read-only in Win XP.

– dlamblin
Jul 10 '13 at 16:10















@kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

– Tim Banchi
Jun 27 '14 at 10:51







@kicsyromy: formatting a partition (sdxN) to UDF did not work, executing sudo mkudffs --media-type=hd --blocksize=512 /dev/sdd1 gives the following error message: trying to change type of multiple extents I did however succeed in formatting UDF using the whole disk (sdd) as described here: superuser.com/questions/39942/using-udf-on-a-usb-flash-drive

– Tim Banchi
Jun 27 '14 at 10:51







protected by Community Mar 19 '15 at 5:06



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?



Popular posts from this blog

GameSpot

日野市

Tu-95轟炸機