Cannot read partitions

[Liam Proven]

On 03/10/2007, Derek Broughton <news at pointerstop.ca> wrote:
> Liam Proven wrote:
>
> > Why jfs? That seems a /very/ strange choice. It's a journalling
> > filesystem type typically used with IBM OS/2. What's wrong with ext3
> > or even reiser?
>
> I can answer that.  I've tried both of those, and XFS.  XFS isn't well
> supported (or rather wasn't a year or so ago) by the installer, so that
> just wasn't an option for initial setup.
>
> Reiser worked for me for years, but a couple of years ago I ran into
> corruption problems, that seemed to be specifically related to Reiser, so I
> went looking for other systems.
>
> ext3 is simply not very efficient, imo.  It's a journal bolted onto an
> ancient filesystem, and while I will guarantee it will work, I have been
> happier with both Reiser & JFS for performance.

All right... But this is serious fiddling you're doing here. I don't
mean to mock, but if you're doing half-hearted mucking around like
trying to convert a Windows partition to a Linux one, you probably
shouldn't be playing with high-end filesystems like jfs.

Be serious: back up any data, reformat the machine, work out a
partitioning scheme (I suggest boot/root/home/swap as a minimum), and
for a desktop machine, use something vanilla like ext3.

JFS is a filesystem for an enterprise server holding a few terabytes.
We're talking large hardware-controlled RAIDs of preferably SAS disks
and JFS volumes layered on top of LVM.

Don't try to convert a machine in place from one OS to another. It's a
recipe for pain, as you're discovering. Back up the data, nuke,
reinstall.

Honestly, trust me. I've been doing stuff like this for 20y. You're
mixing and matching two bad things: [1] in-place OS and filesystem
swaps & [2] inappropriate choice of filesystems.


> I used ntfs-3g for about 6 months, then it started causing corruption on the
> Windows side, and even after everything was apparently fixed using Windows
> Scandisk, only about 50% of the files I tried to read via ntfs-3g could be
> read without IO errors.  I remounted with the read-only NTFS driver and
> could read flawlessly.

Like I said before: don't use NFTS from Linux. If you need shared
access, use FAT32, or better still, put the shared data on a dedicated
fileserver.

-- 
Liam Proven • Profile: http://www.linkedin.com/in/liamproven
Email: lproven at cix.co.uk • GMail/GoogleTalk/Orkut: lproven at gmail.com
Tel: +44 20-8685-0498 • Cell: +44 7939-087884 • Fax: + 44 870-9151419
AOL/AIM/iChat: liamproven at aol.com • MSN/Messenger: lproven at hotmail.com
Yahoo: liamproven at yahoo.co.uk • Skype: liamproven • ICQ: 73187508