Hot answers tagged filesystems
The Unix default permissions for a newly created file are 0666. The Unix default permissions for a newly created directory are 0777. If you do not want the default base permissions set an appropriate umask value. The only thing you can't easily do with umask is create a file which is by default executable (which, by simple common sense, is something you ...
Here is what I use in trying to figure out problems like this. du -s `ls -a | egrep -v '\.\.'` | sort -nr | head It will show you the usage per directory/file in the current directory. From there you step down into sub dirs until you find something obvious. Having everything in one big partition can make diagnosing problems like this difficult. Another ...
No NTFS doesn't calculate a checksum. Take a look at Does Windows calculate CRCs to check every file operation? and in the Wikipedia file comparsion table In the How NTFS Works Technet article you will learn how NTFS works.
There is no one definitive way for them to get out of order, it can happen a few different ways. Some that I've run into: Making a rights change and hitting cancel cancel OMG cancel in a panic before it gets done applying (kinda bad if you do it at the top of a 4-million file directory tree). Command-line utilities (I'm thinking xcacls, I believe) that ...
You can run any filesystem on a bare block device with or without partitions, however the danger is that both people and OSes expect to see a partition table on a block device to realize that there is data present. (both raw disks and partitions are just block devices, after all) ZFS actually creates such a guardian partition table which is why it's safe ...
Not required, but you should partition. The partition table eats up very little space, but it is universally recognizable. Windows will know that there's a filesystem there if you put it in a Windows box. If you have no partitions, other operating systems will just treat it as an empty drive.
It sounds a lot like a similar issue I have all the time with deleted files (but the reference is still there). If we're talking a Linux system, run: lsof +L1 This will be a list of deletes files, but are still open and being used by something. The key is to get whatever has the filehandle open to release it.
@Iain's answer works for any unix. However, in linux you can also specifically allow a group to mount a device. Make the device owned by the group you want to allow to mount it In /etc/fstab, use the option "group" instead of "user" This is described in the man page for mount(8) (instead of the one for fstab, confusingly): FILESYSTEM INDEPENDENT MOUNT ...
You need any file system that supports "punch" to create holes in files where data previously existed. All files systems that support inodes (ext2/3/4, xfs, btfs, etc) support files with holes while creating the files but only recently has there been a way to remove (zero out) data in a way that creates holes. See http://lwn.net/Articles/415889/ If you ...
Yes you can format a whole block device and need not create a partition first. On SAN LUNs and multi-boot systems I would recommend creating partitions though and setting the correct filesystem id, as you run the risk that other operating systems and/or operators could interpret a unpartitioned disk as free and unused.
The usual way to do something like this is to use sudo Create a group and add you privileged users to it. Create a script that does the mount/unmount action Ensure the script is executable but writeable only by root. Edit sudoers to allow the group to execute the script Profit
Only top voted, non community-wiki answers of a minimum length are eligible