@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 repo
@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 problem
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"
everyth
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 med
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
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 t
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 fr
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 be
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 r
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,
portabilit
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
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
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.
--
C
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 partitio
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.ne
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 B
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
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 ar
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.la
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.
--
ubunt
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 mailin
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 partit
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
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
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 m
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-
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 Linu
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.n
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
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_nt
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
https://bugs.launchpad.net/bugs/27901
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
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 notifi
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 fo
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 f
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
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
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 Li
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 Ubunt
> 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
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 driv
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
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 volume
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/33
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
shoul
** 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
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.launchpa
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 Ubu
** 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
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 b
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
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:
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 subsc
** 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.
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
ubuntu-bugs@li
** 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
When you /bin/cp a file then it gets new timestamps by default whatever
is the file system. Nautilus maybe redefines this behaviour but not
consistently.
** Changed in: nautilus (Ubuntu)
Sourcepackagename: ntfs-3g => nautilus
--
Copyng a file to a NTFS drive change the date and the time of the f
If you have an older ntfs-3g release than version 1.328 then the
slowness is an ntfs-3g limitation and you should upgrade to at least
version 1.328 or preferable version 1.417.
The maximum supported NTFS file size and the volume size is 16777216 GB
(16 EByte) but typically your hardware and Linux
Yes, it can happen with any disk which powers down during write
activity, have bad sectors or other hardware fault.. You can find the
proofs in the logs under /var/log/ There isn't absolutely anything
ntfs-3g could do about such problems besides reporting them. They are on
a lower level.
--
ntf
http://ntfs-3g.org/support.html#locale
--
NTFS-3g on boot switch off ru_RU.UTF-8 locale
https://bugs.launchpad.net/bugs/152740
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.co
Please see the most common reasons for high NTFS-3G CPU usage at
http://www.ntfs-3g.org/support.html#cpu100
I also do remember a problem in amarok what one of the above items also
suggests and Waster's comment too who doesn't use NTFS. Maybe you don't
have the fix Sarah mentioned?
--
Amarok hang
So, do you suggest that there is a problem using FLAC files with Amarok
and NTFS-3G? If yes, then please do the following as root at the command
line:
umount
mount -t ntfs-3g -o debug &> ntfs-3g.log
reproduce the problem
umount
and then send here or to [EMAIL PROTECTED] th
Who is using CPU when amarok hangs, and can you find anything in the
/var/log/daemon.log file?
--
Amarok hangs during tagging of FLAC files
https://bugs.launchpad.net/bugs/24063
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for amarok in ubunt
I remember an amarokcollectionscanner high memory usage problem. That
could also cause all kinds of weird problems.
--
Amarok hangs during tagging of FLAC files
https://bugs.launchpad.net/bugs/24063
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contac
Thanks a lot Evgeny. Amarok (or the FLAC codec) indeed uses very
unoptimal write buffer size which significantly worsen the performance:
http://ntfs-3g.org/support.html#dd
--
Amarok hangs during tagging of FLAC files
https://bugs.launchpad.net/bugs/24063
You received this bug notification because
Gparted isn't maintained for a long time and some of the most serious
problems are in Parted actually. I wrote ntfsresize what gparted uses
and explained the problems and how to fix them to the authors many times
but they never got fixed for some reasons.
Regards, Szaka
==
NTFS-3G Lead Developer
Neither ntfs-3g nor fuse bug. The partition is already in exclusive use
by the kernel and you must mount the partition somewhere under
/dev/mapper.
** Changed in: ntfs-3g (Ubuntu)
Status: New => Invalid
--
[GUTSY] Unable to mount NTFS partition
https://bugs.launchpad.net/bugs/151099
You r
Can anybody send an install log? I've never heard about situation where
mount.ntfs (ntfs-3g) would hang, only here. Mount either succeeds or it
fails and the mount command returns. The issue is clearly related to
mount.ntfs, it triggers something somewhere but only the log could tell
where the rea
Anybody knows which package /etc/init.d/mountall.sh belongs? The problem
can't be fixed in the ntfs-3g package, only in the one which
/etc/init.d/mountall.sh has and its maintainer is apparently not aware
of the problem, so he can't fix it.
--
files with unusual character sets are sometimes compl
@Vangelis Tasoulas: can you see the files if you do
umount -a
mount -a
If not then your problem is different, e.g. your locale is not
configured, or doesn't exist, or not the correct one.
==
NTFS-3G Lead Developer: http://ntfs-3g.org
--
files with unusual character sets are sometimes complete
It can't be fixed. Windows is in a mess which can be fixed only by
itself. Mounting the drive is intentionally denied because it would be
highly unsafe and could result full data loss. What I think nobody would
like to happen.
Workaround can be the usage of the 'force' mount option which, as I
men
** Changed in: sysvinit (Ubuntu)
Sourcepackagename: ntfs-3g => sysvinit
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
https://bugs.launchpad.net/bugs/132357
You received this bug notification because you are a member of Ubuntu
Bu
Metadata means that it don't have any user data, only the NTFS
structures.
--
ntfs-3g uses most of the cpu
https://bugs.launchpad.net/bugs/137141
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-b
What's you /etc/fstab? Probably your locale is on a separate partition
which weren't mounted yet when ntfs is mounted. Moving the ntfs-3g entry
to the end of /etc/fstab should help.
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
h
Gutsy uses a very old NTFS-3G which denied several mount scenarios what are
supported now. For example when the NTFS partition was resized previously, or
the Windows hibernation file is corrupted.
There are two problems here:
1) NTFS-3G is tool old
2) Install shouldn't stop if mounting the NTFS
My comment was for the earlier syslog. Is mount.ntfs a symlink to ntfs-
3g? If yes then there are more problems.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you are a member o
Do you have the same problem with not JFS file system too? JFS is dead,
IBM stopped supporting it, so it can have all short of problems, more
and more in time.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received t
If you can make a custom installer then you can use the 'debug' ntfs-3g
mount option and you could see on the stdout (or stderr, depending on
the fuse version used) what's exactly happening with the driver and
where it hangs. Well, actually unless it's in the kernel which is very
probably. How much
@Vangelis Tasoulas: you're not using the NTFS-3G driver but the old
kernel one. Change all occurances of ntfs to ntfs-3g in your fstab file
and everything should be fine if you use the latest gutsy install with
the fix Colin just mentioned.
--
files with unusual character sets are sometimes compl
If you're Greek then the LANG="en_US.UTF-8" setting is not ok. You
should use LANG=el_GR.UTF-8
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
https://bugs.launchpad.net/bugs/132357
You received this bug notification because you ar
What's the output of 'locale -a'?
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
https://bugs.launchpad.net/bugs/132357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
You don't have Greek locale: http://ntfs-3g.org/support.html#locale
I'm surprised you can use them even after umount/mount.
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
https://bugs.launchpad.net/bugs/132357
You received this bu
Please try el_GR.utf8 too. Technically you don't have el_GR.UTF-8 (local
-a output). This shouldn't matter but maybe this legacy support was
broken by a developer accidentally.
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctly
https:
ntfs-3g's fd 3 is the ntfs block device where it read/writes. Anything
else is closed (fd 0,1,2 unless the 'debug' option is used). Logging is
done via openlog(3).
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You receiv
Actually the daemon(3) function is used by default which redirects the standard
fd's to /dev/null:
lrwx-- 1 root root 64 Oct 2 00:58 5 -> socket:[2190855]
lrwx-- 1 root root 64 Oct 2 00:58 4 -> /dev/fuse
lrwx-- 1 root root 64 Oct 2 00:58 3 -> /dev/hda3
lrwx-- 1 root root 64 Oct
Vangelis: Could you try el_GR.utf8 (not el_GR.UTF-8 and not
en_US.UTF-8)? Probably it won't make a difference but if 'locale'
canonicalises differently then perhaps something else too.
--
files with unusual character sets are sometimes completely invisible to the
driver : locale not set correctl
Vangelis: Does it help if you put into /etc/default/locale
LC_ALL="el_GR.UTF-8"
and you export it in /etc/init.d/mountall.sh where the LANG variable exported
too?
export LC_ALL
Though something could still set it (back) to "C" before NTFS mount.
setlocale(3) ignores LANG if LC_ALL is set.
--
f
This is an Ubuntu boot time configuration problem. The locale
environment is set only after the NTFS partition was mounted which is
too late: http://ntfs-3g.org/support.html#locale3
--
ubuntu doesn't see every file on ntfs
https://bugs.launchpad.net/bugs/144813
You received this bug notification
Using strace bunzip2 ... you can see why the kernel doesn't allow you to
do what you want. Bunzip2 wants to set the owner or a permission it's
not authorized to do according to your mount parameters. Set the uid= to
the user you're bunzip2'ing and it will work.
--
bunzip2 cannot extract files
htt
Then you need to fix bunzip2 to work the way as gzip, or turn off NTFS-
3G permission handling completely (no umask=, fmask=, dmask=, uid=, gid=
mount options).
--
bunzip2 cannot extract files
https://bugs.launchpad.net/bugs/146225
You received this bug notification because you are a member of Ub
1 - 100 of 190 matches
Mail list logo
