Tag Info

Hot answers tagged

8

Woohoo, I solved it :) The short answer is you can't mount >4k block size devices on x86 linux machines as far as I can tell without some serious kernel hacking. However, there is a work around.. using fuse-ext2 to mount the disk: fuseext2 -o ro -o sync_read /dev/sdb4 /mnt/ (you'll probably need to apt-get fuseext2 first..) works perfectly first time! ...


4

You're working from a bad premise, being that badblocks can solve your problem in the first place. When badblocks finds bad sectors on the disk, what it is really telling you is that the hard disk has run out of spare sectors, which means that it has been degrading for some time. Up until the point where badblocks can actually detect this, the hard drive ...


2

As per comments rsync is a good tool to use. Basic rsync usage simply mirrors a directory. For example: rsync -aE --delete /source/dir /backup/dir Will make the backup directory match the source; if there is stuff in the backup that isn't in the source, it will be deleted (--delete), and if there is stuff that is in both, it will be updated in the ...


2

The simplest approach, assuming you want to back up folder /foo would be to create a simple little crontab to run rsync daily. Create your crontab by running crontab -e. In the editor window that will appear, add this line (assuming your NAS is mounted locally, you can use ssh if not): @daily rsync -glprtu /foo /path/to/NAS/mount Close the editor window. ...


2

If LVM is nothing for you, why don't you use an aufs (overlay) filesystem. It works like this: user@host:~# mount -t aufs -o br=/mnt/disk1:/mnt/disk2 none /nas/share/ The mount command, specifies it is going to union mount /mnt/disk1/ and /mnt/disk2/ under /nas/share/. The directory /nas/share/ will have the content of both /mnt/disk1/ and /mnt/disk2/. ...


2

Your strategy for naming seems fine. In my department at university, disks are exported similarly as: /machine-name/s0 /machine-name/s1 /machine-name/s2 to all other local machines. This is essentially the same naming scheme you propose. One thing you'll have to consider if you want to access you NAS from multiple machines is consistency of userid ...


1

You are using BusyBox' umount, presumably that one doesn't understand encfs specific flags (and its mount might also do things wrong). Does the encfs package include mount/unmount programs? Better use those. Perhaps you need to build a BusyBox with encfs support?


1

Basically, any ARM compatible distro is worth a try, it does not need to be small, just configurable. I would recommend you go with Arch which installs a minimal system but makes it easy for you to expand it by downloading and installing packages, but the choice is yours. You can find help on installing Debian on your NAS here and a user here reports ...



Only top voted, non community-wiki answers of a minimum length are eligible