When attempting to start the iscsitarget service, I get
FATAL: Module iscsi_trgt not found.
Trying to build module using instructions from http://sourceforge.net/apps/mediawiki/iscsitarget/index.php?title=Unofficial_DEBs fails and the build log only has a single line in it saying the build started. Nothing about the failure.
Unable to access NFS shares on Ubuntu from Windows 7. It just acts like the share can't be found on network. (NET HELP MSG 1222)
on client:
added NFS features
tried "mount IP:/share z:" and the gui drive mapping
tried with and without "AnonymousUid""AnonymousGid" DWORDs under HKLM\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default
on server:
exportfs lists the shares.
mount shows "nfsd on /proc/fs/nfsd type nfsd (rw)" (I think that's normal?!?)
have experimented with many options in:
/etc/exports
/etc/default/nfs-kernel-server
/etc/default/nfs-common
tried forcing no NFS v 4
after each change I'm restarting nfs service and re-exporting
I've been trying to figure this out forever. Any help would be much appreciated!
Are there any IP blocking applications or firewalls that support IPv6?
The ones I know about (pgld, moblock (sunset?) , nfblock, iplist (looks old)) are only for IPv4.
1) Is there a gui or curses tool that allows you to view/manage btrfs subvols/snapshots?
2) Is there a utility or already made script that would automatically create and delete snapshots daily/weekly? I'm aware that I could probably use a simple sh via cron but is there anything more elaborate that already exists?
Using Clonezilla, I cloned a Windows 7 installation from the first partition on one drive to the first partition on a second larger drive and then installed Ubuntu into the second partition (same configuration as the original drive, just newer version instead of old).
Ubuntu detected the Windows 7 partition properly and added it to the grub menu. However, when I choose the win7 option in grub, I just get a black screen and blinking cursor. How can I fix this?
@CentaurusA: Here is the output of boot info script output http://pastebin.com/778RP7Lp
What is wrong with this picture?
Top is output from "df -h", bottom is gparted. I suspect I'm missing a lot of free space. No problems other than that (yet). Can somebody suggest the best (non-destructive) way to correct this?
sudo dumpe2fs -h /dev/sda3: (source http://pastebin.com/nAvrdT4E)
Filesystem volume name: <none>
Last mounted on: /
Filesystem UUID: 9f6eff64-60d7-4eec-81d5-1e8acd818b38
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1602496
Block count: 6406144
Reserved block count: 320306
Free blocks: 4842284
Free inodes: 1361222
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8176
Inode blocks per group: 511
RAID stride: 32692
Flex block group size: 16
Filesystem created: Sun Nov 8 18:18:13 2009
Last mount time: Tue Mar 1 01:04:27 2011
Last write time: Mon Feb 28 04:27:34 2011
Mount count: 16
Maximum mount count: 28
Last checked: Thu Feb 24 06:23:39 2011
Check interval: 15552000 (6 months)
Next check after: Tue Aug 23 07:23:39 2011
Lifetime writes: 227 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 268015
Default directory hash: half_md4
Directory Hash Seed: cc101517-e617-482b-a883-a72919419c84
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x001d3000
Journal start: 7787
fdisk and parted output per requests: http://pastebin.com/EGVH7Ken
SOLUTION: (thanks Hamish Downer) Boot to a liveCD and run "sudo e2fsck -f /dev/sda3" followed by "sudo resize2fs -p /dev/sda3"
I think I'm having difficulty fully understanding subvolumes and snapshots. The /home partition is btrfs. I want to create a "backup" snapshot of /home/user (for example) but user has existed for years (previously ext4 > btrfs-convert). I believe you can only make a snapshot of a subvolume. I checked and there are no "default" subvolumes already present.
1) Is there another way for me to backup /home/user other than creating a subvolume /home/user2 and copying everything from user to user2 in order to snapshot it?
Probably stupid questions but here goes:
Can btrfs use only a portion of a HDD in a raid "array"?
I have 3 HDDs: 80GB, 160GB, and 200GB external USB. I want to put root+boot in the first 20GB of the smallest drive on EXT4 and use the rest of the free space on all 3 drives for a btrfs "raid10 array". Is this possible?
Is this sane? Would you do it differently?