User avatar
Tass
Posts: 535
Joined: Sat Jan 21, 2012 11:15 am

Re: Root filesystem available to download

Tue Feb 21, 2012 1:15 pm

I racked up a mighty 1:1.8 on the first day, but it's hardly moved since then.

rrolsbe
Posts: 40
Joined: Fri Aug 12, 2011 4:09 pm

Re: Root filesystem available to download

Tue Feb 21, 2012 7:49 pm

rrolsbe said:


Hopefully this has not been asked before (I searched the forum), will the EXT4 root file system be mounted noatime, nodiratime, and with the EXT4 journal capability disabled in the currently downloadable .img file?  I am not very familiar with the (De-fragmentation function of EXT4) but maybe that should also be OFF by default if possible.  After-all, minimizing writes to low-end flash boot devices not only increases useful life but should also improve performance somewhat.

Thanks for any Brain cycles in advance!!!

Regards, Ron


Not sure if file system fragmentation on flash media is a big hit on read performance, but it it might be a good idea to de-fragment both the FAT32 and EXT4 partitions immediately before creating the .img file.

# fsck.ext4  /dev/mmcblk0p2
e2fsck 1.41.11 (14-Mar-2010)
/dev/mmcblk0p2 has been mounted 34 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes

Inode 202 was part of the orphaned inode list.  FIXED.
Inode 203 was part of the orphaned inode list.  FIXED.
Inode 204 was part of the orphaned inode list.  FIXED.
Inode 205 was part of the orphaned inode list.  FIXED.

many more not listed....

Inode 206 was part of the orphaned inode list.  FIXED.
Inode 46819 was part of the orphaned inode list.  FIXED.
Inode 46822 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes

Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mmcblk0p2: 46830/101920 files (0.1% non-contiguous), 326333/407040 blocks

# fsck.ext4 -fvn /dev/mmcblk0p2
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

46830 inodes used (45.95%)
31 non-contiguous files (0.1%)  Looks good!!!
6 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 35444/5
326333 blocks used (80.17%)
0 bad blocks
1 large file

31988 regular files
3462 directories
12 character device files
25 block device files
2 fifos
415 links
11331 symbolic links (11331 fast symbolic links)
1 socket
--------
47236 files

User avatar
Feakster
Posts: 35
Joined: Sun Jan 22, 2012 10:41 pm

Re: Root filesystem available to download

Thu May 10, 2012 5:44 pm

errikos said:


I don"t know if this is the right place to ask, but is it possible to have a smaller image for the bootloader only to put in a small SD card, and keep the main filesystem to an external USB hard disk drive? For most multimedia functions, I don"t think that just the SD card will be adequate...

Thanks!


You can do it Yourself. From downloaded image write only first (boot) partition to SD. Create/copy second(root) and swap partitions to external USD hard disk drive. Change path in SD card file cmdline.txt, where root=/dev/mmcblk0p2 to Yours external disk root partition, in most cases root=/dev/sda1. Edit /etc/fstab in root partition changing swap partition path.

Not all files in boot partition are necessary, so SD card size can be 16MB.

Would you possibly be able to give a step by step guide on how to do this? I think it"s something that a lot of people will want to do. I personally haven"t got a clue how... Please please please...

Return to “General discussion”