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 shaky premise, being that badblocks can solve your problem in the first place. Why badblocks Is an Untrustworthy Repair Method As you use a hard drive, it continually does its best to hide problems from you by swapping fresh sectors in for dodgy ones. The hard disk ships from the factory with a pool of spare sectors for this very ...


2

As per comments rsync is a good tool to use. Basic rsync usage simply mirrors a directory. For example: rsync -a --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 backup ...


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

The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).


1

This is an error in the networking code path and has no relation to hardware issue by itself. I doubt you have much of a concern there with regard to the device itself. You can check if you have network packet drops that may cause a problem using ethtool -S and on the other network devices just in case. It is possible that you have some network issue or ...


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

How can I debug this? Try to strace the command. That should show the syscalls the program is making, which could help you narrow it down.


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