|
From: Anton A. <ai...@ca...> - 2008-05-09 09:42:05
|
Hi, If you mount read-only then you will completely avoid this problem as it only affects the write code path. Best regards, Anton On 9 May 2008, at 09:44, Jeremy Bennett wrote: > Thanks for the explanation. I can upgrade to a newer kernel in-house. > > I'm using the ancient kernel for backward compatibility with > customers (most > of whom use RHEL3 and none of whom have progressed passed RHEL4). > Will I be > safe(r) if I mount NTFS partitions read-only? It's very useful to > take a > dual-boot laptop to a customer site with a compatible version of > Linux on > it. > > Thanks, > > > Jeremy > > -------------------------------------------------- > Tools and Models for Embedded Software Development > > Tel: +44 1202 416955 > Cell: +44 7970 676050 > SkypeID: jeremybennett > Email: jer...@em... > Web: www.embecosm.com > > -----Original Message----- > From: Anton Altaparmakov [mailto:ai...@ca...] > Sent: 09 May 2008 09:05 > To: jer...@em... > Cc: lin...@li... > Subject: Re: [Linux-NTFS-Dev] Problem with NTFS mounted partition > > Hi, > > You are using an ancient kernel. This has been fixed years ago... > > Thanks for the report anyway! > > Best regards, > > Anton > > On 8 May 2008, at 16:16, Jeremy Bennett wrote: > >> I had problems with an NTFS partition mounted under Centos 4.6. Here >> is the entry from dmesg >> >> NTFS-fs error (device hdb1): write_mft_record_nolock(): Writing mft >> records without existing buffers is not implemented yet. Please >> email >> lin...@li... and say that you saw this >> message. >> Thank you. >> NTFS-fs error (device hdb1): ntfs_write_inode(): Failed (error code >> 95): >> Marking inode as bad. You should run chkdsk. >> NTFS-fs error (device hdb1): write_mft_record_nolock(): Writing mft >> records without existing buffers is not implemented yet. Please >> email >> lin...@li... and say that you saw this >> message. >> Thank you. >> NTFS-fs error (device hdb1): ntfs_write_inode(): Failed (error code >> 95): >> Marking inode as bad. You should run chkdsk. >> >> Output from uname -a >> >> Linux ramsey 2.6.9-67.0.7.ELsmp #1 SMP Sat Mar 15 06:54:55 EDT 2008 >> i686 >> i686 i386 GNU/Linux >> >> Running on an Intel Core 2 Duo box. >> >> I'll run chkdsk now. Let me know if you need any more information. >> >> Jeremy Bennett -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
