*** 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
*** 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
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
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
** 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
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
** 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
** 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,
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
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
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
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
** 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
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
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
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()
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
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
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
** 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
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)
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
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
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 '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
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
@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
@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
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
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
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
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
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
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.
--
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.
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
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
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
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
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
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.
--
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
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
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.
--
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
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
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
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
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
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
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.
--
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-
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
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
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
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 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
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
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.
--
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,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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-
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
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
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
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
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
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.
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
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
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.
--
*** 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
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
@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
1 - 100 of 191 matches
Mail list logo
