Apr 092008

Short article about how to enable a Debian Etch (stable version at moment of writing) to have access in read/write to NTFS filesystems.

Since there is not package available in standard Etch repositories, packages needs to be retrieved and installed by “Etch Backports” repositories as follows:

  • wget http://www.backports.org/debian/pool/main/f/fuse/fuse-utils_2.7.1-2~bpo40+1_i386.deb
  • wget http://www.backports.org/debian/pool/main/f/fuse/libfuse2_2.7.1-2~bpo40+1_i386.deb
  • wget http://www.backports.org/debian/pool/main/n/ntfs-3g/libntfs-3g2_1.516-1~bpo.1_i386.deb
  • wget http://www.backports.org/debian/pool/main/n/ntfs-3g/ntfs-3g_1.516-1~bpo.1_i386.deb

Then, set’em up in your Debian using following commands:

  • dpkg -i libfuse2_2.7.1-2~bpo40+1_i386.deb
  • dpkg -i fuse-utils_2.7.1-2~bpo40+1_i386.deb
  • dpkg -i libntfs-3g2_1.516-1~bpo.1_i386.deb
  • dpkg -i ntfs-3g_1.516-1~bpo.1_i386.deb

Then test mounting it using command:

mount -t ntfs-3g /dev/sda1 (replace /dev/sda1 with your device) /<mounting path>

It might come up with following message if your kernel is still the standard one of Etch version… should be harmless if you’re just mounting an NTFS formatted external drive as I’m trying to…
WARNING: Deficient Linux kernel detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it’s made sure the ntfs-3g process
naturally terminates after calling ‘umount’. If you wish this
message to disappear then you should upgrade to at least kernel
version 2.6.20, or request help from your distribution to fix
the kernel problem. The below web page has more information:

Mar 292008

One of the things I like of Linux is that despite I’m working with it since 1994 I never end learning part of it.

Today my need was the following: I dd a 20 Gb backup onto a 40 Gb HDD and it worked smoothly, but problem is that filesystem on first partition was 20 Gb while partition was 40 Gb (more or less).

Therefore my need was to extend my filesystem to match partition size to benefit of the additional disk space offered by new HDD size. Googling a bit, I discovered a command that did the magic very smoothly: resize2fs.
All I needed to do is launching command followed by device where filesystem needs to be resized, no matter is filesystem is mounted or not, as follows: resize2fs /dev/hda1

Output has pleasantly been the following:

resize2fs 1.40-WIP (14-Nov-2006)
Filesystem at /dev/hda1 is mounted on /; on-line resizing required
old desc_blocks = 2, new_desc_blocks = 3
Performing an on-line resize of /dev/hda1 to 8835742 (4k) blocks.
The filesystem on /dev/hda1 is now 8835742 blocks long.

Useless to say that AFAIK on Windows this is a dream without costly softwares, and even then…