How to make file writable linux

How to make read-only file system writable?

At some point, the filesystem on my digital audio player has become read-only. I cannot copy files into it or remove files on it. Are there some possible reasons for the player’s file system to change permissions in this way? I tried using chmod :

$ sudo chmod a+rw SGTL\ MSCN/ chmod: changing permissions of `SGTL MSCN/': Read-only file system 

Could you also add brand of the player? 🙂 searching ‘SGTL MSN’ actually ONLY brings up this topic 😀 If you are really unlucky it’s the device that’s bugged: as a last(!) resort reset the player. But only when you do not get any good anwsers soon(ish) 🙂

Tried everything, and found a simple solution (heretic). Plug the usb to windows 8 or 7, click «repair external drive», go back to linux. Hope this helps someone.

7 Answers 7

If a filesystem has been mounted read-only, chmod will not work since it’s a write operation too.

Try remounting it read-write:

sudo mount -o remount,rw '/media/SGTL MSCN' 

If the device has a write lock on it (like SD memory cards), you need to turn it off. Hardware locks cannot be disabled by software. Note that the write lock on SD memory cards is located from the sight you see the letters near the up left corner and it looks like a very small switch.

Some filesystem drivers may also not support write operations, this is the case with the older NTFS module supported by Linux. For NTFS filesystems, be sure to use the ntfs-3g driver which should be picked automatically nowadays. If not, you can force the driver with something like:

sudo mount -t ntfs-3g -o uid=$(id -u) /dev/sdb1 /mnt/ 

(where /dev/sdb1 has to be substituted for your block device and /mnt/ for your destination)

@XavierStuvw If read/write protected means readonly, ok. Otherwise you could try to wipe it and repurpose it. The wipefs command can be used on a partition to ensure that no filesystem is recognized. See man wipefs (part of util-linux).

@JoshuaSalazar how did you mount it? Perhaps you could create a new question and include such details, this comment section is getting a bit too large.

For NTFS file systems this problem may occur when it is not properly unmounted (probably by unexpected shutdown of windows). In such cases the file systems are marked as locked.

You can mount them properly using the following ntfsfix command, for example:

Please replace /dev/sda3 with your own device name.

I’d like to add for future Googlers that doing this fixed the «New Steam library folder must be on a filesystem mounted with execute permissions» on Manjaro Linux and it’s probably the same for other distros.

Thanks for this! I’m dual booting Kubuntu and Windows 10 and I could not understand why sometimes I’m unable to mount a disk with write permissions!

I had this problem occur on several USB sticks. Each time I searched for an answer and tried various suggestions, including using Terminal to run commands, reformatting on both Linux and Windows machines, etc. All to no avail.

It happened to me again today so again I went looking to see if I could find a solution. I tried the things here, but they didn’t work.

Out of desperation I again went to Disk Utility. I unmounted the drive and then hit «Format» on the partition portion, not the drive portion — USB only had the single partition. This time it WORKED. Then I went to the drive portion and again reformatted the single partition as a master boot drive and monkeyed a bit more with it.

The upshot is, I’m now able to read and write to the drive again.

I don’t know if I just got lucky this time or not. But it is working again.

Источник

Thread: Command to make a file writable?

First Cup of Ubuntu

Command to make a file writable?

(First post. Woo. Also, if this happens to be the wrong catagory. well, my bad.)

Since there has to be a command for this, what’s the command for making a read-only file writable? I need it becuase I’m trying to change my default window manager back to Gnome, since I can’t get X to start, but the file containing that precious setting? Read-only.

Dark Roasted Ubuntu

Re: Command to make a file writable?

will give the owner of file the permission to write to it.

will give the owner and group of file permission to write to it.

Take the risk of thinking for yourself, much more happiness, truth, beauty, and wisdom will come to you that way. —Christopher Hitchens

First Cup of Ubuntu

Re: Command to make a file writable?

As for my little X issue, I got it working. Thank you failsafe backup xorg.conf file!

• Site Areas
• Settings
• Private Messages
• Subscriptions
• Who’s Online
• Search Forums
• Forums Home
• Forums
• The Ubuntu Forum Community
  1. Ubuntu Official Flavours Support
     1. New to Ubuntu
     2. General Help
     3. Installation & Upgrades
     4. Hardware
     5. Desktop Environments
     6. Networking & Wireless
     7. Multimedia Software
  2. Ubuntu Specialised Support
     1. Ubuntu Development Version
     2. Security
     3. Virtualisation
     4. Ubuntu Servers, Cloud and Juju
        1. Server Platforms
        2. Ubuntu Cloud and Juju
     5. Gaming & Leisure
        1. Emulators
     6. Wine
     7. Development & Programming
        1. Packaging and Compiling Programs
        2. Development CD/DVD Image Testing
        3. Ubuntu Application Development
        4. Ubuntu Dev Link Forum
        5. Programming Talk
        6. Repositories & Backports
           1. Ubuntu Backports
              1. Bug Reports / Support
     8. System76 Support
     9. Apple Hardware Users
  3. Ubuntu Community Discussions
     1. Ubuntu, Linux and OS Chat
        1. Recurring Discussions
        2. Full Circle Magazine
     2. The Cafe
        1. Cafe Games
     3. Market
     4. Mobile Technology Discussions (CLOSED)
     5. Announcements & News
     6. Weekly Newsletter
     7. Membership Applications
     8. The Fridge Discussions
     9. Forum Council Agenda
     10. Forum Feedback & Help
         1. Request a LoCo forum
     11. Resolution Centre
  4. Other Discussion and Support
     1. Other OS Support and Projects
        1. Other Operating Systems
           1. Ubuntu/Debian BASED
           2. Debian
           3. MINT
           4. Arch and derivatives
           5. Fedora/RedHat and derivatives
           6. Mandriva/Mageia
           7. Slackware and derivatives
           8. openSUSE and SUSE Linux Enterprise
           9. Mac OSX
           10. PCLinuxOS
           11. Gentoo and derivatives
           12. Windows
           13. BSD
           14. Any Other OS
     2. Assistive Technology & Accessibility
     3. Art & Design
     4. Education & Science
     5. Documentation and Community Wiki Discussions
     6. Tutorials
        1. Outdated Tutorials & Tips
     7. Ubuntu Women
     8. Ubuntu LoCo Team Forums
        1. Americas LoCo Teams
           1. Argentina Team
              1. Software
              2. Hardware
              3. Comunidad
           2. Arizona Team — US
           3. Arkansas Team — US
           4. Brazil Team
           5. California Team — US
           6. Canada Team
           7. Centroamerica Team
           8. Chile Team
              1. Comunidad
              2. Hardware
              3. Software
              4. Instalaci�n y Actualizaci�n
           9. Colombia Team — Colombia
           10. Georgia Team — US
           11. Illinois Team
           12. Indiana — US
           13. Kentucky Team — US
           14. Maine Team — US
           15. Minnesota Team — US
           16. Mississippi Team — US
           17. Nebraska Team — US
           18. New Mexico Team — US
           19. New York — US
           20. North Carolina Team — US
           21. Ohio Team — US
           22. Oklahoma Team — US
           23. Oregon Team — US
           24. Pennsylvania Team — US
           25. Peru Team
           26. Texas Team — US
           27. Uruguay Team
           28. Utah Team — US
           29. Virginia Team — US
           30. West Virginia Team — US
        2. Asia and Oceania LoCo Teams
           1. Australia Team
           2. Bangladesh Team
           3. Hong Kong Team
           4. Myanmar Team
           5. Philippine Team
           6. Singapore Team
        3. Europe, Middle East, and African (EMEA) LoCo Teams
           1. Albania Team
           2. Catalan Team
           3. Portugal Team
           4. Egypt Team
           5. Georgia Team
           6. Ireland Team — Ireland
           7. Kenyan Team — Kenya
           8. Kurdish Team — Kurdistan
           9. Lebanon Team
           10. Morocco Team
           11. Saudi Arabia Team
           12. Sudan Team
           13. Tunisia Team
        4. Other Forums & Teams
        5. LoCo Archive
           1. Afghanistan Team
           2. Alabama Team — US
           3. Alaska Team — US
           4. Algerian Team
           5. Andhra Pradesh Team — India
           6. Austria Team
           7. Bangalore Team
           8. Bolivia Team
           9. Cameroon Team
           10. Colorado Team — US
           11. Connecticut Team
           12. Costa Rica Team
           13. Delhi Team
           14. Ecuador Team
           15. El Salvador Team
           16. Florida Team — US
           17. Galician LoCo Team
           18. Greek team
           19. Hawaii Team — US
           20. Honduras Team
           21. Idaho Team — US
           22. Iowa Team — US
           23. Jordan Team
           24. Kansas Team — US
           25. Libya Team
           26. Louisiana Team — US
           27. Maryland Team — US
           28. Massachusetts Team
           29. Michigan Team — US
           30. Missouri Team — US
           31. Montana Team — US
           32. Namibia Team
           33. Nevada Team — US
           34. New Hampshire Team — US
           35. New Jersey Team — US
           36. Northeastern Team — US
           37. Panama Team
           38. Paraguay Team
           39. Qatar Team
           40. Quebec Team
           41. Rhode Island Team — US
           42. Senegal Team
           43. South Carolina Team — US
           44. South Dakota Team — US
           45. Switzerland Team
           46. Tamil Team — India
           47. Tennessee Team — US
           48. Trinidad & Tobago Team
           49. Uganda Team
           50. United Kingdom Team
           51. US LoCo Teams
           52. Venezuela Team
           53. Wales Team
           54. Washington DC Team — US
           55. Washington State Team — US
           56. Wisconsin Team
           57. Yemen Team
           58. Za Team — South Africa
           59. Zimbabwe Team

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts

vBulletin �2000 — 2023, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical � Canonical Ltd. Tango Icons � Tango Desktop Project.
User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. For details and our forum data attribution, retention and privacy policy, see here

Источник

How to make an ext4 file writable on mounting by a user (not root)

I think your fmask option is too strict and gives no read permission on files to group and other . Set it to fmask=000 or just leave it out to get rw- permissions on all files. You shouldn’t have executable permissions by default.

Also, I think the gid option only accepts group id numbers, so it should read gid=100 instead. And you should add the rw option (I forgot mentioning that).

No need to add rw . It’s the default behaviour. It’s ro that must be specified explicitly. However, users should be user .

3 Answers 3

You can’t; ext[234] doesn’t support the uid/gid options or any other way of overriding the on disk permissions at mount time. You must set the permissions correctly on the disk as root.

A similar question came up to me on [How fstab mount options work together with per file defined permissions in linux and got a detailed answer by the community!

The thing with etx4 is that the mount options in fstab are used in combination to the permissions stored for each file. This is of course contrary to NTFS that does not have any linux permissions associated per file and thus takes such arguments from the fstab mount options only.

So, in order to make a file stored in an EXT4 filesystem writable by a certain user you need to both:

1) mount the disk with rw or defaults to enable writing to the filesystem in general AND

2) have a set of permissions set for each file such as the user CAN write to it, this can be achived with various ways..

a)If the file is owner by the user and write permission is granted to the owner

[sudo] chown user:user file
[sudo] chmod u+w file

b)If the file is owned by the group the user belongs to and write permission is granted to the group

[sudo] chown other_user:users file
[sudo] chmod g+w file

c) if the file is granted permission to write by anyone:

Источник