[Bug 562139] Re: FUSE filesystems cannot be accessed when shared
*** This bug is a duplicate of bug 175689 *** https://bugs.launchpad.net/bugs/175689 On Tuesday 13, April, Chow Loong Jin wrote: crippled filesystem (driver)s that do not implement ownership and/or permissions properly. For the record, NTFS-3G developers has ported the POSIX File System Test Suite to Linux and ensured NTFS-3G passes all ownership and permission tests successfully. Unlike some non-crippled file system drivers which were fixed later. http://www.tuxera.com/community/posix-test-suite/ -- FUSE filesystems cannot be accessed when shared https://bugs.launchpad.net/bugs/562139 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu (via bug 175689). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 562139] Re: FUSE filesystems cannot be accessed when shared
*** This bug is a duplicate of bug 175689 *** https://bugs.launchpad.net/bugs/175689 On Tuesday 13, April, Chow Loong Jin wrote: crippled filesystem (driver)s that do not implement ownership and/or permissions properly. For the record, NTFS-3G developers has ported the POSIX File System Test Suite to Linux and ensured NTFS-3G passes all ownership and permission tests successfully. Unlike some non-crippled file system drivers which were fixed later. http://www.tuxera.com/community/posix-test-suite/ -- FUSE filesystems cannot be accessed when shared https://bugs.launchpad.net/bugs/562139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 514223] Re: Vista, Windows Server 2008 and Windows 7 unable to access devices touched by ntfs-3g versions prior to 2010.1.16
Some correction to the bug report from the NTFS-3G developers: 1. It is not true that Vista, Windows Server 2008 and Windows 7 unable to access devices touched by ntfs-3g versions prior to 2010.1.16. Just try and you will see that all of them will see the NTFS partition fine. The fact is that there is a slight chance in a very special case that this will happen. How often? Perhaps once in 10 million cases. 2. It is not true that NTFS-3G created volumes can not be accessed on Windows. NTFS-3G doesn't create NTFS volumes, it's mkntfs from the ntfsprogs package which does. Nevertheless we are not aware that mkntfs has any problem you mention. -- Vista, Windows Server 2008 and Windows 7 unable to access devices touched by ntfs-3g versions prior to 2010.1.16 https://bugs.launchpad.net/bugs/514223 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412119] Re: Copying NTFS partition full might cause NTFS errors
Please see http://ntfs-3g.org/support.html#indexo ** Changed in: ntfs-3g (Ubuntu) Status: New = Invalid -- Copying NTFS partition full might cause NTFS errors https://bugs.launchpad.net/bugs/412119 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389718] Re: Ntsf-3g is corrupting NTFS structure.
** Changed in: ntfs-3g (Ubuntu) Status: New = Invalid -- Ntsf-3g is corrupting NTFS structure. https://bugs.launchpad.net/bugs/389718 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396874] Re: mount ignores options from fstab
http://ntfs-3g.org/support.html#wine It's a mount(8) bug/feature. Use 'users,exec', not 'exec,user'. ** Package changed: ntfs-3g (Ubuntu) = util-linux (Ubuntu) -- mount ignores options from fstab https://bugs.launchpad.net/bugs/396874 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368134] Re: nfts-3g ubuntu 9.04 filesystem corruption
** Changed in: ntfs-3g (Ubuntu) Status: New = Invalid -- nfts-3g ubuntu 9.04 filesystem corruption https://bugs.launchpad.net/bugs/368134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318625] Re: Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?; question mark) when ripping to NTFS volumes
** Package changed: ntfs-3g (Ubuntu) = rhythmbox (Ubuntu) -- Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?; question mark) when ripping to NTFS volumes https://bugs.launchpad.net/bugs/318625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162863] Re: ntfs-3g does not respect fstab options
http://ntfs-3g.org/support.html#useroption2 -- ntfs-3g does not respect fstab options https://bugs.launchpad.net/bugs/162863 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368134] Re: nfts-3g ubuntu 9.04 filesystem corruption
What NTFS-3G does is actually detects and reports that something has corrupted two files. The 2.6.28-11 causes massive data corruption with ICH8/ICH9 on 64 bits installations bug is indeed a very good candidate to be the real culprit. Data and file system corruptions almost exclusively origin from a hardware, device driver, kernel problem or user problem (e.g. unsafe detach of a hardware). NTFS-3G has extensive and redundant data integrity and consistency checking and often finds and reports them. -- nfts-3g ubuntu 9.04 filesystem corruption https://bugs.launchpad.net/bugs/368134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 336762] Re: ntfs hard links not working
Ubuntu doesn't compile with the internal FUSE library which is used to ensure and certify NTFS-3G quality. The external FUSE library has several issues which are fixed only in the FUSE CVS. -- ntfs hard links not working https://bugs.launchpad.net/bugs/336762 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 336762] Re: ntfs hard links not working
The problem can not be reproduced with NTFS-3G 2009.2.1, internal FUSE and kernel 2.6.26. NTFS-3G and/or the kernel is too old in Ubuntu 8.10. Upstream NTFS-3G has closed this issue report as INVALID and Ubuntu specific. -- ntfs hard links not working https://bugs.launchpad.net/bugs/336762 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 336762] Re: ntfs hard links not working
** Changed in: ntfs-3g (Ubuntu) Sourcepackagename: util-linux = ntfs-3g -- ntfs hard links not working https://bugs.launchpad.net/bugs/336762 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 336762] Re: ntfs hard links not working
Hard links work fine (you can confirm by ls -i after cp -al) but probably the 'echo B B' case doesn't because apparently the '' creates a new file for some reason. Do you have any specific software which doesn't work correctly with NTFS-3G? -- ntfs hard links not working https://bugs.launchpad.net/bugs/336762 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
This is a known Vista problem handling sparse files. Please contact Microsoft. Good luck! -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330023] Re: ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup()
NTFS-3G 2009.2.1 did fix a crash in ntfs_attr_lookup if a file or directory (this is the case here) was highly fragmented and there was an NTFS corruption or hardware problem: http://ntfs-3g.org/releases.html -- ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup() https://bugs.launchpad.net/bugs/330023 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330023] Re: ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup()
The crash happens exactly at the same place which was fixed in NTFS-3G 2009.2.1. However the stack trace doesn't look correct. There are some problems with it. Like apparently using debug symbols from the NTFS-3G 2009.2.1 release and manual edition of vital parameters to corrupt values which should never happen. -- ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup() https://bugs.launchpad.net/bugs/330023 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250060] Re: ntfs-3g crashed with SIGSEGV in ntfs_log_handler_syslog()
Not ntfs-3g specific, other programs crash in syslog - dl_fixup() too: Bug #188354, Bug #279586, Bug #124453 ** Changed in: glibc (Ubuntu) Sourcepackagename: ntfs-3g = glibc -- ntfs-3g crashed with SIGSEGV in ntfs_log_handler_syslog() https://bugs.launchpad.net/bugs/250060 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175503] Re: User-friendly automounting of ntfs partitions with an unclean logfile
NTFS-3G solved this issue from version 2009.2.1: http://ntfs- 3g.org/releases.html -- User-friendly automounting of ntfs partitions with an unclean logfile https://bugs.launchpad.net/bugs/175503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310326] Re: Intrepid: USB HDD not mounted
** Changed in: hal (Ubuntu) Sourcepackagename: ntfs-3g = hal Status: Incomplete = Confirmed -- Intrepid: USB HDD not mounted https://bugs.launchpad.net/bugs/310326 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240429] Re: adding files to mercurial repository fails on ntfs
The driver works as expected (Operation not permitted). Remove the
default_permissions option then it should work. Please see more detail
about permission handling in the NTFS-3G manual ('Access Handling and
Security' section): http://ntfs-3g.org/manual.html
** Changed in: ntfs-3g (Ubuntu)
Status: New = Invalid
--
adding files to mercurial repository fails on ntfs
https://bugs.launchpad.net/bugs/240429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328352] Re: mount.ntfs causes 100% CPU (iowait)
It's not clear what you copied from where to where and how. Anyway it looks to be a hardware problem. Check your RAM and disks for bad sectors, e.g. by the utility badblocks. -- mount.ntfs causes 100% CPU (iowait) https://bugs.launchpad.net/bugs/328352 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328352] Re: mount.ntfs causes 100% CPU (iowait)
It's impossible to see what NTFS-3G has to do with the problem. Yes, the /dev/sda1 NTFS partition is mounted at /media/WindowsRecovery by NTFS-3G but you were reading from another file system mounted at /media/mobile120 and writing to partition /dev/sda2. The IOWAIT is completely normal when one is copying data. If no disk activity than that's usually a hardware or kernel device driver problem, most typically USB problem when an external device is involved. Like it disconnected, auto-suspended, etc. Did you check your kernel logs? mount.ntfs in the process list is completely normal when at least one partition is mounted. Th FUSE daemon speculation doesn't stand either. The only FUSE daemon is mount.ntfs which can not deadlock itself, especially when it's not used for anything. -- mount.ntfs causes 100% CPU (iowait) https://bugs.launchpad.net/bugs/328352 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322751] Re: Not mounting drives unsafely removed in windows is an annoying default
Joseph: This is a long and complex story. I make it short. I've seen many thousands related comments, suggestions, arguments in the last many years but yours was the first one which had a good point (case 3). Theoretically you're not right but practically you are: the damage was already done when the user unsafely detached the drive. The next release of the official NTFS-3G will mount all such problematic volumes read-write by default. Thanks. Regards,Szaka == http://ntfs-3g.org -- Not mounting drives unsafely removed in windows is an annoying default https://bugs.launchpad.net/bugs/322751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320192] Re: ntfs-3g doesn't support exec option
The 'exec' mount option is of course supported. In fact it's the default NTFS-3G option. There are over 80 NTFS-3G mount options. These are NTFS- 3G, FUSE user space, FUSE kernel driver and kernel VFS related. The NTFS-3G man page documents only the NTFS-3G specific mount options, none of the other ones like, 'exec'. The supported mount options always depend on the NTFS-3G version, the FUSE user space version, FUSE kernel module version and the kernel version. But users should never neet to know more then perhaps some of the NTFS-3G specific one and the general kernel options (uid, gid, exec, suid, etc). Please also not blame NTFS-3G for the current problem. It is HAL. We tried hard to push for a trivial and transparent solution but the HAL maintainer decided to make life much harder for everybody: http://lists.freedesktop.org/archives/hal/2008-October/012366.html http://lists.freedesktop.org/archives/hal/2008-October/012368.html Notice, how I predicted that the HAL changes will break many distributions: See e.g. Danny's recent reverted patch. The next HAL release will break at least all Ubuntu and Fedora based distros (about 12 million users) not being able to automount NTFS. Again. HAL is historically a highly unreliable and confusing solution. Afaik, much better alternatives are being worked on. Btw, the latest NTFS-3G release (2009.1.1) has built-in, transparent UTF-8 support and the locale= option is ignored for filename conversion. The locale= option didn't work in many cases eve if it was correctly passed to NTFS-3G (and that is a glibc problem but that's another very long story). -- ntfs-3g doesn't support exec option https://bugs.launchpad.net/bugs/320192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318625] Re: Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?; question mark) when ripping to NTFS volumes
This is definitely not an NTFS-3G problem. The '?' is a perfectly legal NTFS character in the POSIX namesspace NTFS-3G uses: http://ntfs- 3g.org/support.html#posixfilenames2 -- Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?; question mark) when ripping to NTFS volumes https://bugs.launchpad.net/bugs/318625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250705] Re: Please backport ntfs-3g
@Shirish: NTFS-3G is a user space driver. It can't hang the system. Only buggy kernels can. Nevertheless your experience is very unique and it sounds to be a hardware problem. It's also possible that Ubuntu patched the driver and something went terrible wrong. But then, much more people would report this problem but so far you're the only one. -- Please backport ntfs-3g https://bugs.launchpad.net/bugs/250705 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303610] Re: file move causes data loss if interrupted due to system crash
@Florian Linux NTFS development claims 100% NTFS compatibility. If you think otherwise then please describe here what your problems are because we very much would like to know and fix it if it's justified. Please note, Ubuntu uses an extremely old version of the driver which indeed has many problems which were already solved very long ago: http://ntfs- 3g.org/releases.html @kyferez Moving a file is irrelevant of the file system. It's an application level issue. The software gives the orders and the file system driver (like NTFS-3G) executes them. This is how file managers always work during cross-device move (you assumption is horrible wrong!): 1. copy the file to the destination 2. sync the file to the disk on the destination 3. remove file from the source How can this go wrong? It's the 2. point in the hardware. The disk caches data and it doesn't flush them to the platter when the software asks but it lies it's already there to improve performance. This is not an Ubuntu or Linux issue. It's not even an NTFS issue. It happens all the time with all operating systems and all file systems. Here are some examples: OS X: http://it.slashdot.org/article.pl?sid=07/11/05/2328259 Windows: http://support.microsoft.com/kb/940508 Regards, Szaka == NTFS-3G: http:/ntfs-3g.org -- file move causes data loss if interrupted due to system crash https://bugs.launchpad.net/bugs/303610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303610] Re: file move causes data loss if interrupted due to system crash
Things don't work the way you think. They are much, much more complex. E.g. a full NTFS driver implementation requires more than 150 person years work. Not only the file data but ALL relevant metadata must be on the disk as well. If only a few metadata bytes are missing then one may lose everything, or some files, or part(s) of a file or nothing. It depends on what part of the metadata was not flushed to the disk. This is the reason why a recovery software can recover files by scanning the entire disk. Most files are there but the pointers to them are not correct and they are not visible and accessible by the user. -- file move causes data loss if interrupted due to system crash https://bugs.launchpad.net/bugs/303610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303610] Re: file move causes data loss if interrupted due to system crash
No software solution will help because the (disk) caches will lie about the data. It's not possible to build a reliable (predictable) system on unreliable hardware. People want the cheapest and fastest disks = disk manufacturers provide them but data unreliability is the real price. The faster media wearing is another serious, increasing reliability problem. Battery backed disk controllers could help the issue but during a power outage quite many other things can go wrong in the hardware. Cheap, personal PCs are not designed to work reliably in such conditions because the hardware price would rocket what most people couldn't not afford. Buying and using an UPC is much cheaper. Invent a cheap, fast, reliable data storage and you will become a billionaire. Today everybody must choose two from the tree and leave with the consequences. -- file move causes data loss if interrupted due to system crash https://bugs.launchpad.net/bugs/303610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303610] Re: file move causes data loss if interrupted due to system crash
It's mathematically not possible, not statistically. If Windows were safe Microsoft wouldn't have documented the same data loss problem: http://support.microsoft.com/kb/940508 They talk about not unmounted devices which is the same as suddenly removing them or power outage. Moreover the severity of the data loss also depends how the file system is mounted, sync or not. The former has poor performance but minimizes data loss. The later has much better performance but much more things can get lost if the hardware or power fails. Windows typically uses the former, meanwhile Ubuntu the later because system crashes are not very common use case scenarios on Linux systems. -- file move causes data loss if interrupted due to system crash https://bugs.launchpad.net/bugs/303610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
It's possible that this is a pure Windows bug. Either a Microsoft NTFS or a device driver related. Google found many similar crashes but none of them involved NTFS-3G, only for Windows recovery. Here is an idea how we could prove and document this is a pure Windows bug. 1. Install Cygwin (a Linux-like environment for Windows): http://www.cygwin.com/ 2. Create the file which BSOD Vista. 3. Copy the file on Windows using cygwin 'cp' command the below way: cp --sparse=always 001.part 001.part.win 4. Ntfsclone the NTFS volume for potential later investigation. 5. Replace 001.part (this shouldn't change the problematic NTFS metadata): rename 001.part 001.part.linux rename 001.part.win 001.part 6. Continue the download on Windows. If Vista BSOD then it's proven that this is a pure Vista bug and unrelated to NTFS-3G. If it works then please send the NTFS debug image file you got in step 4. Thanks! -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
The ZIP package at http://www.flexhex.com/docs/articles/download/sparse.zip contains a CS.EXE file which is supposed to work similarly as the cygwin cp --sparse=always command. The test could be simpler. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
I've found the below on http://channel9.msdn.com/forums/Coffeehouse/256701-QuickTime-BSODs- Vista-solution That eMule had to remove all the sparse file support on Vista because of Vista bugs So, it's very well possible this is a pure Vista bug what any software can trigger, not only NTFS-3G. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Cygwin cp --sparse=always doesn't work. The files are not sparse. CS.EXE also doesn't work on my x64 because it's a 32-bit EXE file. Maybe you're more lucky. Of course it's also possible that Microsoft silently disabled sparse file support because they had too many reliability problems with them. File system development is not too easy. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
No such problem was reported with XP. Sparse support can't be disabled for NTFS-3G because it's part of the POSIX specification. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
What are the outputs of ntfs-3g.probe --readwrite /dev/sda5 ntfs-3g.probe --readonly /dev/sda5 Yes, the log file is important even if we can't create yet the NTFS debug file. We will make a solution for you depending on the above results. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Storno the ntfs-3g.probe's. I just realized you use ntfsprogs-2.0.0 and have problem with the image file, not the NTFS device. Please use ntfsclone from ntfsprogs 1.13.1. ntfsprogs-2.0.0 has problems. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Well, if the journal file is unclean then ntfsclone-1.13.2-wip will fail too. There are two choices: 1. Run ntfsfix on /dev/sda5 before running ntfsclone (any version). 2. Run ntfsfix on ntfsmeta.img then ntfsclone ntfsmeta.img. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Use the --force option. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Good job! :-) Yes, bzip2 is unfortunately very slow. We will solve this issue in the future by using a different NTFS debug image format. The actions are correct. I would also need the output of egrep -3i 'ntfs|ata|sd|i/o' /var/log/daemon.log and the name of the file which crashes Vista. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Please download http://ntfs-3g.org/download/ntfsclone-1.13.2-wip.tgz Unpack it and use ntfsclone-1.13.2-wip instead of ntfsclone. Thanks. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Please also send the output of egrep -i 'ntfs|ata|sd|I/O' /var/log/daemon.log /var/log/daemon.log could be also /var/log/messages, /var/log/messages.log, /var/log/syslog or something else distribution specific. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
I'll make you an ntfsclone binary which you can use, please wait a bit. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Yes, --force ntfs-3g mount and unmount should also fix it. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
NTFS interoperates with several other subsytems and if one of them fails then the problem appears as an NTFS bug but in fact it isn't. That's why more, non-NTFS info is needed, to confine where the problem is. The good news is that no sign of any hardware problem. However it seems the NTFS partitions are not unmounted properly, or at all by Ubuntu. This can indeed cause NTFS corruptions. This seems to happen all the time at least with /dev/sda1. The situation is also strange with /dev/sda5 because it was only unmounted once, yesterday night (besides your today's mount/unmount which is there in the log fine) but I can't see when and how /dev/sda5 was mounted. Earlier than 3th of October? Then how could you report the problem yesterday? So something seems to be very strange about how Ubuntu handles mounts and unmounts. The NTFS debug info files should reveal more. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
The file metadata is indeed inconsistent. Did you start to download the file in Linux or Vista? What is your Vista version? Do you have Vista Patches, Service Packs? -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Yes, chkdsk has many problems unfortunately. If it still crashes then no need for the other debug file. What are the Amule versions for Windows and Linux? You don't have Windows Home Server, do you? Microsoft is having major problems with NTFS file corruptions and they even had to hire back one of their main NTFS architects recently. http://support.microsoft.com/kb/946676 http://blogs.zdnet.com/Bott/?p=473 Some of their corruptions are related to compressed files, and it seems, this is the case here too. But I don't have any clue why they made the file quasi-compressed (corrupted metadata) instead of continuing the file updates as non-compressed, as Linux started. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
That would be a very good observation! If BSOD comes when you copy the file then please run the below command in Linux shell. It is one line: for i in $(seq 1 200); do dd if=/dev/zero of=sparse bs=4096 seek=$((2*$i)) count=1 conv=notrunc; done Then try to copy the 'sparse' file on Windows. If it also BSOD then we are much closer. Thanks! No, the file is not compressed, it's sparse only. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
On Wed, 8 Oct 2008, [utf-8] Nicolò Chieffo wrote: Do you think that sparse files are wrongly managed by ntfs-3g? They are fine. But your case is more complex than the usual one. It also could be a unique, subtle problem. Nobody else reported this problem and I also can't reproduce it. This might be true, since when the file is completed (and though re-created) it does not cause any BSOD. If the file caused BSOD but When it's ready and no problem then please run ntfsinfo -fv -F file_name device on Linux and sent th efull output. Do you know if amule can be set up to not create sparse files? if so we could also test if started files can be resumed by emule without any problems. I don't know if amule suports this. But I think the issue is sparse file related. I will also test the following: start the file in emule, resume in amule and test back what emule does Ok. Wait: can't it be that emule does not use sparse file, and amule does? so emule accesses the file normally which causes the page fault! Sparse file handling is transparent and a user space application definitely shouldn't crash the OS. This is a serious Microsoft bug but we need to figure out where the real problem is. A file system driver should never crash, not even with corrupted files and data. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Can you write down the Vista BSOD messages, or make a photo about it? -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Thank you for the bug report. The NTFS-3G project is very interested to help you to solve your problem. Please follow the below steps to be able to help you: 1. Reproduce the problem. 2. Create the NTFS debug information according to http://www.linux- ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata 3. Run 'chkdsk DRIVE: /F' and reboot into Windows to make it an effect. 4. Repeat step 1. 5. Try to reproduce the problem on Windows. 6. Send the files you got in step 1. and 3. to szaka AT ntfs-3g.org or make them available somewhere for download and let us know if step 3 helped. Thank you, Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
Sorry, step 4 had a typo, it should be: 4. Repeat step 2. It's important to create the NTFS debug info right after running CHKDSK and before trying to reproduce the problem. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279017] Re: sharing amule temp files winth Vista in ntfs partition gives BSOD
And of course step 6 was supposed to say: 6. Send the files you got in step 2. and 4. to szaka AT ntfs-3g.org or make them available somewhere for download and let us know if step 3 helped. -- sharing amule temp files winth Vista in ntfs partition gives BSOD https://bugs.launchpad.net/bugs/279017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269946] Re: open(filename, O_DIRECT) on ntfs fails
Thanks. The issue is added to the TODO list. NTFS-3G never supported O_DIRECT. It was just an accident that it (incorrectly) worked in the past which, it seems, was fixed by the kernel. -- open(filename, O_DIRECT) on ntfs fails https://bugs.launchpad.net/bugs/269946 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269946] Re: open(filename, O_DIRECT) on ntfs fails
Can you reproduce with non-swap files too? If the swap is on then the error is correct (protects from crash, system corruption) though I think the errno is indeed misleading (it's a kernel problem). -- open(filename, O_DIRECT) on ntfs fails https://bugs.launchpad.net/bugs/269946 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250597] Re: Cannot mount ntfs partition as only writable by 1 user
This is a kernel problem which was (supposedly) fixed silently in the recent kernel security upgrade. Probably it's time to submit a CVE for it ... -- Cannot mount ntfs partition as only writable by 1 user https://bugs.launchpad.net/bugs/250597 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250597] Re: Cannot mount ntfs partition as only writable by 1 user
Ok, I see. Not even one user can write to the partition? Well, Ubuntu is using an old, unsupported, custom patched and uncertified NTFS-3G driver with external FUSE. If the configuration is not right then this problem can indeed happen. I suggest removing the Ubuntu NTFS-3G package and installing it from the source: http://ntfs-3g.org/ Besides solving dozens of reliability and security problems, it's also fully supported by upstream. -- Cannot mount ntfs partition as only writable by 1 user https://bugs.launchpad.net/bugs/250597 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250597] Re: Cannot mount ntfs partition as only writable by 1 user
On Tue, 22 Jul 2008, themuddler wrote: The problem isn't that not-even-one can write, but that any user can read/write when it's supposed to be accessible by just 1 user (the owner). This is what I answered originally. Upgrade your kernel to the fixed one and your problem is gone. -- Cannot mount ntfs partition as only writable by 1 user https://bugs.launchpad.net/bugs/250597 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204133] Re: wubi install unusable - Buffer I/O error on device loop0
Nice work. Colin, FUSE doesn't support sync(2) but the 'sync' mount option should be ok because FUSE writes are always synchronous at the moment. Your patch fundamentally solved ntfs-3g 'sync' support minus some issues (cached metadata, disk caching, propagating the sync option to FUSE, portability, maybe others). The patch is planned to be applied with some modifications within about a month as 'sync' mount option support. Could you please point out where sync(2) is needed in FUSE if this is the case, or what do you mean it doesn't support what would be needed for more reliable WUBI operation? I think this would be a strong reason to raise the implementation priority. The 'sync' performance impact is 20-3,000% depending on the workload but it was never more than 200% during normal usages. -- wubi install unusable - Buffer I/O error on device loop0 https://bugs.launchpad.net/bugs/204133 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243287] Re: Copying files from Linux to NTFS Partition (using NTFS-3G) makes random-placed non-movable system blocks which causes file fragmentation
Here are some info what kind of fragmentations exist. It's important to read because fragmentation types are often misunderstood: http://en.wikipedia.org/wiki/Fragmentation_(computer) The NTFS-3G driver tries hard not to fragment files and if you're doing a lot of concurrent writes then you will find that it's much more efficient than the Microsoft NTFS driver which fragments files usually at every 16 clusters meanwhile NTFS-3G fragments them only at around 4000 clusters. This means the elimination of 250 very costly, slow disk seeks and result much better write and read performance. What you're seeing is external fragmentation. The NTFS-3G driver indeed places different files a bit far from each other to eliminate and optimize file fragmentation to improve the disk performance. How much does it matter? Usually technically and performance wise it's absolutely irrelevant. If you don't believe me then please feel free to send your NTFS debug info to szaka AT ntfs-3g.org folllowing the instructions at http://www.linux-ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata and I will tell you the TRUTH about your real fragmentation and what you can check yourself to be true by reading all the open source code we are using to do these REAL analyzes. About the system blocks. These are always Windows deficiencies explained nicely to Windows users. There are many reasons for them. For instance files in use by Windows are unmovable. Sadly Windows caches a lot of attributes absolutely needlessly and prevents defragmenters to do their jobs. The built-in Windows defragmenter code, what all the Windows defragmenters use, apparently also has technical limitations, like not being able to relocates files having attribute list attribute. In such case they don't say We are very sorry, this functionality is not implemented! but instead System block. So users won't be upset with Microsoft but try to find somebody else to blame and people always do: the defragmenter, a file system driver, etc. What you can do is offline defragmentation, i.e. Windows should not be running during the process. Regards, Szaka -- NTFS-3G Lead Developer: http://ntfs-3g.org -- Copying files from Linux to NTFS Partition (using NTFS-3G) makes random-placed non-movable system blocks which causes file fragmentation https://bugs.launchpad.net/bugs/243287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242426] Re: Ark hangs when file/directory name on NTFS contains a colon
http://ntfs-3g.org/support.html#posixfilenames2 Why does the driver allow special characters in the filenames? NTFS supports several filename namespaces at the same time: DOS, Win32 and POSIX. While the NTFS-3G driver handles all of them, it always creates new files in the POSIX namespace for maximum portability and interoperability reasons. This means that filenames are case sensitive and all characters are allowed except '/' and '\0'. This is perfectly legal on Windows, though some application may get confused. If you find so then please report it to the developer of the relevant Windows software. Workaround: If case insensitivity handling and/or restriction of special character usage is desirable then you may export the NTFS volume via Samba which supports this functionality the same way as it does for other POSIX file systems. Status: Not NTFS-3G problem. -- Ark hangs when file/directory name on NTFS contains a colon https://bugs.launchpad.net/bugs/242426 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199161] Re: File and directory removal, rename and move may have been denied with an Operation not supported error message
http://ntfs-3g.org/support.html#compressed -- File and directory removal, rename and move may have been denied with an Operation not supported error message https://bugs.launchpad.net/bugs/199161 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237575] Re: Not ext2/ext3 drivers for other operating systems available when you format an external HDD or USB stick
Reading more about the open source NTFS-3G driver, I have to add that apparently it neither supports change of file owner nor access rights, so IMHO NTFS is no option for the Ubuntu user. On the NTFS-3G home page at http://ntfs-3g.org the first link in the first paragraph points to NTFS-3G with full file ownership and access right support: http://pagesperso-orange.fr/b.andre/security.html -- Not ext2/ext3 drivers for other operating systems available when you format an external HDD or USB stick https://bugs.launchpad.net/bugs/237575 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232443] Re: Let the user choose between ntfs-3g and ntfs kernel driver
By default the kernel driver mounts read-only, NTFS-3G read-write. Mounting read-write turns on a lot of consistency checks to protect against potential data corruptions during write. But of one uses the 'ro', read-only mount option then NTFS-3G will mount the volume the same way as the kernel driver. Yes, many people are not aware of this, or know how to use mount options. Because of this, NTFS-3G will fall back to read-only mount automatic by default in the future versions when read-write mount is unsafe. -- Let the user choose between ntfs-3g and ntfs kernel driver https://bugs.launchpad.net/bugs/232443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232443] Re: Let the user choose between ntfs-3g and ntfs kernel driver
Hi, I'd like to ask, why do you want to use the NTFS kernel driver? NTFS-3G can be also used read-only with the 'ro' mount option but a memory corruption can not lead to system crash or data corruption on the disk unlike in case of the NTFS kernel driver. Fundamentally NTFS-3G is the five years old, rewritten NTFS kernel driver plus three years more work: bug fixes, new features, actively developed/maintained, etc. Thanks, Szaka == NTFS-3G: http://ntfs-3g.org -- Let the user choose between ntfs-3g and ntfs kernel driver https://bugs.launchpad.net/bugs/232443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232443] Re: Let the user choose between ntfs-3g and ntfs kernel driver
CPU usage: - Until very recently Ubuntu indeed used an old, very CPU consuming driver. - The NTFS-3G CPU usage is visible in the process list which is not true for kernel drivers. This makes some people think that the driver uses a lot of CPU even if sometimes it uses less than the in-kernel Linux file systems. - Some more are listed on http://ntfs-3g.org/support.html#cpu100 - The priority of the project is reliability. When we must chose between stability/correctness or performance then we always select the first one. No exception. We improve performance only if it doesn't impact the formers in any way. - The driver is not optimized yet. This will happen when the time comes. Sluggish directory listing: Well, nobody reported this yet. Probably you mean latency. NTFS-3G indeed reads all files before showing the first one. So the delay usually is longer but afterwards it must be smoother. Kernel/user-space difference: Yes, there are quite a lot of myths unfortunately. Some short reading: http://lkml.org/lkml/2008/4/18/136 Data corruptions with 'ro' drivers: All kernel drivers are in the same, unprotected address space. If one has a bug then anything can go wrong anywhere. These do happen all the time. More readings: http://pages.cs.wisc.edu/~swift/ Regards, Szaka -- Let the user choose between ntfs-3g and ntfs kernel driver https://bugs.launchpad.net/bugs/232443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232443] Re: Let the user choose between ntfs-3g and ntfs kernel driver
Sorry, this is the link I originally intended to send in my last comment: http://pages.cs.wisc.edu/~swift/projects/drivers.html -- Let the user choose between ntfs-3g and ntfs kernel driver https://bugs.launchpad.net/bugs/232443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230906] Re: Using special characters in filenames prevents Windows from opening
http://ntfs-3g.org/support.html#posixfilenames2 Why does the driver allow special characters in the filenames? NTFS supports several filename namespaces at the same time: DOS, Win32 and POSIX. While the NTFS-3G driver handles all of them, it always creates new files in the POSIX namespace for maximum portability and interoperability reasons. This means that filenames are case sensitive and all characters are allowed except '/' and '\0'. This is perfectly legal on Windows, though some application may get confused. If you find so then please report it to the developer of the relevant Windows software. Workaround: If case insensitivity handling and/or restriction of special character usage is desirable then you may export the NTFS volume via Samba which supports this functionality the same way as it does for other POSIX file systems. Status: Not ntfs-3g problem. -- Using special characters in filenames prevents Windows from opening https://bugs.launchpad.net/bugs/230906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106621] Re: Gnome Trash doesn't show deleted files on ntfs-3g partitions
Could someone modify the ntfs-3g package so that the hack is directly implemented when the fstab is written? Sadly we can not do anything in NTFS-3G because, as it was earlier explained and patches submitted, this is not an NTFS-3G bug but a Gnome one. When it's possible we always workaround in bugs in applications but I'm sorry to say, we can't do it this time. We also think it's fairly unfortunate how Gnome works because it's not the behavior many Ubuntu users expect and they do keep losing files because of this. Regards, Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- Gnome Trash doesn't show deleted files on ntfs-3g partitions https://bugs.launchpad.net/bugs/106621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106621] Re: Gnome Trash doesn't show deleted files on ntfs-3g partitions
why would users delete files exactly? when there is no trash available nautilus display a dialog explaining that and ask for confirmation to the users By accident. Childen. Elder people. Users who think they can recover from the Trash if they still change their mind. Software bugs. Hung then recovered X/OS/etc and when people desperately hitting/clicking everything to happen something during the temporary freeze time. People in hurry. People in panic. Visually impaired people. And so on. -- Gnome Trash doesn't show deleted files on ntfs-3g partitions https://bugs.launchpad.net/bugs/106621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226622] Re: Wubi has unclear error message on NTFS dirty flag
Both ntfs-3g and ntfs-3g.probe could be used and both return error code 15 if the journal is unclean: http://linux.die.net/man/8/ntfs-3g.probe The most important thing is gracefully shut down and detaching external devices as Microsoft and drive manufacturers has documented. -- Wubi has unclear error message on NTFS dirty flag https://bugs.launchpad.net/bugs/226622 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
I would suspect ntfs to be contributing to the issue but the other identical psc has the same issue though it doesnt not need to be power cycled as often. I can assure you the issue absolutely has nothing to do with NTFS. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190329] Re: DAC permissions not correctly enforced
I can't see problems in your debug session. Your umask setting causes the permission denied errors, no 'x' on the directories. Try e.g. fmask=337,dmask=227 with the 'ro' mount and it will work fine. Similar logic for 'rw' mounts. -- DAC permissions not correctly enforced https://bugs.launchpad.net/bugs/190329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190329] Re: DAC permissions not correctly enforced
Search for the FUSE kernel module default_permission fix. -- DAC permissions not correctly enforced https://bugs.launchpad.net/bugs/190329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223280] Re: rdiff-backup fails on file with unknown unicode character
See http://ntfs-3g.org/support.html#locale -- rdiff-backup fails on file with unknown unicode character https://bugs.launchpad.net/bugs/223280 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190329] Re: DAC permissions not correctly enforced
Fixed in kernel 2.4.25. -- DAC permissions not correctly enforced https://bugs.launchpad.net/bugs/190329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190329] Re: DAC permissions not correctly enforced
Fixed in kernel 2.6.25. -- DAC permissions not correctly enforced https://bugs.launchpad.net/bugs/190329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190329] Re: DAC permissions not correctly enforced
Fixed in kernel 2.6.25. -- DAC permissions not correctly enforced https://bugs.launchpad.net/bugs/190329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203540] Re: ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc)
If ntfs-3g crashes then please send to [EMAIL PROTECTED] the NTFS information according to http://www.linux-ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata and the compressed /var/log/daemon.log file. Otherwise we can't help. Nobody else is having this problem, so you're the only one who can provide us the needed debug information for investigation. Regards, Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc) https://bugs.launchpad.net/bugs/203540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 205081] Re: ntfs-3g will mount as root only, breaks mounting as user
but also to use the external fuse libs It needs internal fuse. The external fuse (suid-root fusermount) has know potential exploits, ntfs-3g doesn't have any. So the safe internal fuse replaces the insafe external fuse. Regards, Szaka == NTFS-3G Lead Developer: http://nts-3g.org -- ntfs-3g will mount as root only, breaks mounting as user https://bugs.launchpad.net/bugs/205081 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195420] Re: moving files with special characters fails
This is because ntfs-3g is ignoring locales Ntfs-3g **never** ignores locale. It's not setup. Regards, Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- moving files with special characters fails https://bugs.launchpad.net/bugs/195420 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210528] Re: ntfs-3g mounted with both options relatime and noatime
Actually there are two problems here: 1. The extra added noatime option which is fixed in NTFS-3G CVS. 2. The atime-relatime change which is a problem in the mount(8) utility because it doesn't pass the atime option to NTFS-3G, so it defaults to relatime. -- ntfs-3g mounted with both options relatime and noatime https://bugs.launchpad.net/bugs/210528 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210528] Re: ntfs-3g mounted with both options relatime and noatime
This is already fixed in the NTFS-3G CVS and will be included in this month of NTFS-3G release. Thanks. -- ntfs-3g mounted with both options relatime and noatime https://bugs.launchpad.net/bugs/210528 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210630] Re: Gutsy version of NTFS allows improper characters in file names
This is 100% intentional, documented at http://ntfs-3g.org/support.html#posixfilenames2 and in fact Windows can access them fine for example by the Windows port of ntfsprogs. -- Gutsy version of NTFS allows improper characters in file names https://bugs.launchpad.net/bugs/210630 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203540] Re: ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc)
On Mon, 31 Mar 2008, lozioric wrote: What Windows version (XP, Vista, Service Packs, etc) do you use? XP Pro SP2, Italian, with up-to-date security updates. Did you use a 3rd party NTFS driver (Partition Magic, Ghost, security software, etc)? I had used Acronis TrueImage once on the affected disk, but I had run Ok, Acronis is known to have problem with NTFS. Chkdsk on it a couple of times since, so it hardly matters IMHO. Chkdsk is not reliable. It also has several known problems. Unfortunately I don't have the disk with me, nor will I for some days. In the meantime it is being used with other Windows boxes (all XP SP2, same as above). Will the info still be useful if I send them in a week or so? Yes, it would be useful if you can still reproduce the problem (what you should). No problem when you can do it since I'm fairly sure the problem is Acronis related which is not used by many people. Your problem is unique. Thanks. -- ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc) https://bugs.launchpad.net/bugs/203540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186117] Re: Cannot remount ntfs
Unfortunately neither fuse nor ntfs-3g support remount at the moment. The working rw-ro case is by pure accident and could lead to data loss. -- Cannot remount ntfs https://bugs.launchpad.net/bugs/186117 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203540] Re: ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc)
Thanks for the bug report. What Windows version (XP, Vista, Service Packs, etc) do you use? Did you use a 3rd party NTFS driver (Partition Magic, Ghost, security software, etc)? Could you please send to [EMAIL PROTECTED] the extracted NTFS information according to http://www.linux- ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata and the compressed /var/log/daemon.log file for debugging? Thanks, Szaka -- ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc) https://bugs.launchpad.net/bugs/203540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 208804] Re: error message mounting suspended disk
Ubuntu uses a very old version of ntfs-3g. The message in the latest ntfs-3g releases is The NTFS partition is hibernated. Please resume and shutdown Windows properly, or mount the volume read-only with the 'ro' mount option, or mount the volume read-write with the 'remove_hiberfile' mount option For example type on the command line: mount -t ntfs-3g %s %s -o remove_hiberfile -- error message mounting suspended disk https://bugs.launchpad.net/bugs/208804 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186569] Re: cannot delete files off of an Fuse mounted NTFS partition in nautilus
Sebastien Bacher wrote: That's a ntfs-3g issue, rmdir on an existant directory returns EEXIST and not ENOTEMPTY as it should You're quite mistaken. Both are correct and file systems use both values: http://www.opengroup.org/onlinepubs/007908775/xsh/rmdir.html NTFS-3G uses EEXIST because more software handle the relevant error scenario better that way. Seemingly that doesn't include Nautilus. Szaka -- NTFS-3G Lead Developer: http://ntfs-3g.org -- cannot delete files off of an Fuse mounted NTFS partition in nautilus https://bugs.launchpad.net/bugs/186569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190667] Re: Cannot copy all files between NTFS disks
You did your tests with the two years old, obsolote, not production quality ntfsmount. Stable read/write NTFS support is provided by a completely different NTFS driver, called NTFS-3G and it's built-in into Ubuntu 7.10. The correct command to use the default Ubuntu NTFS driver is mount -t ntfs-3g /dev/sdb1 /media/sdb1/ or ntfs-3g /dev/sdb1 /media/sdb1/ or probably only mount /dev/sdb1 /media/sdb1/ -- Cannot copy all files between NTFS disks https://bugs.launchpad.net/bugs/190667 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184820] Re: cannot mount NTFS partition as a normal user
http://ntfs-3g.org/support.html#useroption -- cannot mount NTFS partition as a normal user https://bugs.launchpad.net/bugs/184820 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180620] Re: Double mount in one directory
This is how Linux mount works. Bye, Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org ** Changed in: ubuntu Status: New = Invalid -- Double mount in one directory https://bugs.launchpad.net/bugs/180620 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179910] Re: Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition
Stephen: The problem is not Windows but certain Windows softwares which intentionally ignore such files. NTFS-3G doesn't create files in the POSIX namespace to annoy people. Actually it's just the opposite! This way things can Just Work on Linux, Windows, OS X, FreeBSD, NetBSD, OpenSolaris, etc. It is for maximum interoperability what all these OSes support on the file system level, including the Windows operating system. If the driver would create files in a limited namespace then tremendous amount of Linux softwares would break mysteriously, occasionally with data loss. That would be way much worse than the fake error messages from some broken Windows softwares which could be easily fixed. Bye,Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition https://bugs.launchpad.net/bugs/179910 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179910] Re: Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition
Well, it seems to be stupidly false for you because you didn't made the effort to understand what NTFS namespaces are and how file system drivers and applications use them. It __IS__ possible to create files with all the characters you mentioned on Windows and it __IS__ possible to read/rename all these files on Windows which were created on Linux. This just __DEPENDS_ON__ how a given Windows application implemented file handling. You're beating a dead horse because the real problem is not on the Linux but on the Windows side. You're arguing introducing a silliness on Linux instead of you would urge Windows developers to fix their broken softwares which they could very easily done by properly prefixing filenames. -- Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition https://bugs.launchpad.net/bugs/179910 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179910] Re: Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition
Explorer is long known to be broken. This is not surprising because Microsoft is very much interested NOT to interoperate well with other systems on this level to lock users to their platform. You also still don't seem to understand that the only Windows softwares which can't handle such filenames are the ones which DO NOT WANT to handle them. -- Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition https://bugs.launchpad.net/bugs/179910 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179910] Re: Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition
http://ntfs-3g.org/support.html#posixfilenames2 -- Ubuntu should, in some way, handle Windows rules for file names on a NTFS partition https://bugs.launchpad.net/bugs/179910 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 I can tell you that the issue has really absolutely nothing to do with ntfs-3g. It's the kernel how it (incorrectly?) started to setup raid, dm, ldm, etc. The device busy always means that something already locked a device, so it's either already mounted (not in this case) or some kernel subsystem uses it (you must mount some other device, not what you want, e.g. /dev/md0*, /dev/mapper/balblabla*, etc). It really depends on what you have. Szaka == NTFS-3G Lead Developer: http://ntfs-3g.org -- NTFS-3G does not mount external disc in kernel 2.6.22 https://bugs.launchpad.net/bugs/165154 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148949] Re: Windows partitions not accessible
The relevant device is already locked by probably the device mapper, LDM or md. Look for mountable devices under /dev/mapper. kpartx -a /dev/mapper/brand_blabla may be needed to create the mountable partitions under /dev/mapper. In the other two cases follow the relevant instructions how to create a mountable device or what to mount. -- Windows partitions not accessible https://bugs.launchpad.net/bugs/148949 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24063] Re: Amarok hangs during tagging of FLAC files
@apecar: If you have 90+% NTFS-3G CPU usage then please send the debug log following the instructions at https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/24063/comments/9 and after that the full output of egrep -i 'dma|sd|ntfs' /var/log/daemon.log* -- Amarok hangs during tagging of FLAC files https://bugs.launchpad.net/bugs/24063 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
